[EMAIL PROTECTED] wrote:
>
> Rob Siemborski schrieb am Fri, Dec 07, 2001 at 09:53:33PM -0500:
> * saslauthd links the pam libraries just like libsasl used to in SASLv1.
> *
> * libsasl2 now connects to a unix domain socket, which saslauthd is
> * listening to, presents the username and password, and saslauthd consults
> * pam, and replies either yes or now. This is similar to how pwcheck works.
> *
> * To start saslauthd, you give it a password checking mechanism (e.g. pam or
> * rimap or kerberos4 or shadow, such as:
> *
> * saslauthd -a shadow
>
> I *strongly* recommend a change of saslauthd's man page.
>
> Yesterday I migrated from SASL-1.5.27 to SASL-2.0.5-BETA and found it very
> difficult to have my old LDAP-via-PAM authentication scheme survive this
> transition.
>
> As "getpwent" did not work either, I ended up in putting my small LDAP
> userbase back up into the flat files and bring my services up working again
> via "saslauthd -a shadow".
>
> The saslauthd man page did not say *anything* about PAM so I did not try
> that as an option. The methods mentioned there are
>
> "sasldb", "dce", "getpwent", "kerberos4", "rimap", "shadow" and "sia".
I think that this is because the preformatted saslauthd.8 in the
distribution hasn't been updated from the saslauthd.mdoc source. If you
have the mdoc macros, just run:
nroff -mdoc saslauthd.mdoc > saslauthd.8
make install
This will install the latest manpage. Either Rob or myself will fix
this for the next release.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
