For a very good justification of using saslauthd going forward, see the
thread in this mailing list on signaled to death by 11. Some of us are
trying to get Cyrus to authenticate against LDAP. In this case, it is
necessary for cyrus to act as an SASL client to LDAP as well as an SASL
server. It avoids problems to have the password checking done in a separate
process, SASL does not need to act as client and server in the save process
space.
So to counter your assertion: saslauthd can add stability to the system.
Cheers
Chris Audley
----- Original Message -----
From: "Christopher Wong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 12:09 PM
Subject: Re: FAQ: What is saslauthd?
>
> Let me clarify my assertion. My reasoning is this: if a privileged
> daemon adds no functionality nor security to the system, why run it?
> That is why I called pwcheck "practically useless".
>
