Re: qmail-pop3d-ssl no longer works after converting userpass to {SASL}principal <at> realm
Claudio Jeker <jeker <at> n-r-g.com>
2006-06-01 17:29:01 GMT
On Thu, Jun 01, 2006 at 01:26:09AM -0700, jay alvarez wrote:
> Hi,
>
> I have an existing qmail-ldap installation with
> userPasswords in hash.. However, I have decided to
> implement a much more secure authentication using
> kerberos. I'm only running smtpd and qmail-pop3d-ssl
> which can successfully authenticate users via ldap
> lookup. However, I needed to sync our kerberos and
> ldap passwords so what I did was to change the
> userPassword into the format: userPassword:
> {SASL}principal <at> REALM. To my understanding, this
> kerberos passthru format means that authentication via
> search and compare will not work anymore. Perhaps this
> is why qmail-pop3d-ssl didn't work anymore. But after
> reverting the password back to hash format, it
> authenticated the user successfully.
>
>
> Needless to say, I need to find an alternative to
> those daemons. Here are my requirements:
>
> It can offer pop3,imap, and smtp(auth) with ssl and
> can authenticate users via kerberos or ldap binds.
>
>
> We have clients with Windows workstations and I need
> to recommend them to use a particular pop3/imap/smtp
> client with full kerberos/ldap(bind) support. Also,
> the tickets must come from those that have been
(Continue reading)