Am Fr, den 11.03.2005 schrieb Aleksandar Milivojevic um 21:36:
> I believe I had it working with both shadow and pam on FC2 and FC3
> boxes. When set to shadow, it simply reads /etc/shadow directly. When
> set to pam, it will use whatever PAM mechanism is configured on the
> system (for example, lookup users in NIS or NIS+ domains).
Correct.
> However, the system where I tested shadow as saslautd mechanism had only
> crypted passwords in /etc/shadow. I don't know if shadow mechanism
> works with MD5 passwords. If not, time to fill bug report ;-)
No need to fill out a bug ticket. The sentence "/etc/sysconfig/saslauthd
is distributed with MECH=shadow even though cyrus-imapd needs this value
set to MECH=pam" by James B. Byrne is simply not true. I have more than
1 system running with shadow as the saslauthd mechanism, and it works as
it should.
Alexander
--
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.10-1.770_FC2smp
Serendipity 03:12:26 up 2 days, 7:24, load average: 0.66, 0.71, 0.61
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.caosity.org/pipermail/centos/attachments/20050312/5d924543/attachment-0001.bin
