On Fri, 2006-09-29 at 16:24 +0200, Marten Lehmann wrote:
> Hello,
>
> > that would be a problem
>
> I ment: would _not_ be a problem
Then you shouldn't use sasldb. If you don't want regular system
accounts, you can use saslauthd w/PAM, and with PAM use modules such as
pam_userdb[1] or pam_pwdfi
Hello,
that would be a problem
I ment: would _not_ be a problem
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Hello,
it seems that sasldb stores all password in cleartext. Is it possible
to use md5 or crypt as in /etc/passwd?
Not without breaking non-plaintext mechanisms like CRAM-MD5 and DIGEST-MD5.
that would be a problem, we currently support PLAIN only and don't
intent to allow anything else (w
Marten Lehmann wrote:
Hello,
it seems that sasldb stores all password in cleartext. Is it possible to
use md5 or crypt as in /etc/passwd?
Not without breaking non-plaintext mechanisms like CRAM-MD5 and DIGEST-MD5.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Car
> -Original Message-
> it seems that sasldb stores all password in cleartext. Is it
> possible to
> use md5 or crypt as in /etc/passwd?
No, it's not. The entire point is to enable using CRAM-MD5 and other
such mechanisms which require access to the plain-text password. The
advantage o