also sprach Rupa Schomaker <rupa-list@rupa.com> [2003.01.27.1652 +0100]: > It is nearly impossible to get sasl to work *correctly* in a chroot > and even more difficult with PAM. Which is, I believe, why saslauthd was created - to load the authentication off to another software outside the chroot. There is absolutely no documentation though. > I just run it outside of it's jail... Also, you cannot use anything > but PLAIN auth (plaintext userid/passwd in a base64 string) if you > use PAM. Probably not a good idea. If you use sasldb (or sasldb2) > then you can use things like CRAM-MD5. Why not? Is there any way to synchronize the /etc/shadow and /etc/sasldb passwords? I am asking because my users finally learnt how to use the passwd binary. I can't expect them to know anything else. -- Please do not CC me! Mutt (www.mutt.org) can handle this automatically. .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The pgp.net keyservers and their mirrors are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc
Attachment:
pgpHxa1baDerS.pgp
Description: PGP signature