The library comes from CMU:
http://asg.web.cmu.edu/sasl/sasl-library.html

It should just be some 1.5.x release of Cyrus SASL.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of Frank Balluffi
Sent: Friday, August 02, 2002 12:35 PM
To: Sam Hartman <hartmans
Cc: Christian; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: GSSAPI / Native Kerberos API


I see that the extra binary libsasl contains sasl_* functions, but am
not able to find these functions in the source tree. Where are these
functions? Where does this library come from? Thanks.

Frank



 

                      Sam Hartman

                      <[EMAIL PROTECTED]        To:       "Christian"
<[EMAIL PROTECTED]>                                            
                      >                        cc:
[EMAIL PROTECTED]

                      Sent by:                 Subject:  Re: GSSAPI /
Native Kerberos API                                              
                      kerberos-admin@mi

                      t.edu

 

 

                      07/24/2002 02:58

                      PM

 

 





>>>>> "Christian" == Christian  <[EMAIL PROTECTED]> writes:

    Christian> Hello, I'm thinking of kerberizing our application, and
    Christian> i've just read about GSSAPI, which looks like a common
    Christian> interface to C/S authentication. My question is :
    Christian> should I choose GSSAPI or the native Kerberos API ?


You should choose SASL (RFC 2222) if it works for your application.
If that fails, you should use GSSAPI; if your applications requires
services that neither GSSAPI nor SASL can provide then you should use
raw Kerberos calls.

Using SASL (or SASL and TLS as IMAP, LDAP, BEEP and SMTP do) will
provide the greatest flexibility for your application including
support for all SASL and GSSAPI mechanisms.

________________________________________________
Kerberos mailing list           [EMAIL PROTECTED]
http://mailman.mit.edu/mailman/listinfo/kerberos




--

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.


________________________________________________
Kerberos mailing list           [EMAIL PROTECTED]
http://mailman.mit.edu/mailman/listinfo/kerberos

________________________________________________
Kerberos mailing list           [EMAIL PROTECTED]
http://mailman.mit.edu/mailman/listinfo/kerberos

Reply via email to