Just upgrading to 1.0.0 and I'm trying to switch from PAM (using pam-mysql) to a direct mysql query from dovecot, and I've got both md5crypt and crypt passwords in a password db. http://wiki.dovecot.org/Authentication/PasswordSchemes seems to indicate that I have to pick 1, but that is per auth-worker, right? So, I created 2 auth workers using 2 dovecot-sql config files specifying different default encryption schemes and it seems to work. Is there any problem with this, other than a small bit of overhead for 2 queries if the first doesn't hit? Thanks, Ken Anderson Pacific.Net
On Fri, 2007-04-13 at 15:04 -0700, Ken Anderson wrote:> Just upgrading to 1.0.0 and I'm trying to switch from PAM (using > pam-mysql) to a direct mysql query from dovecot, and I've got both > md5crypt and crypt passwords in a password db.md5crypt and crypt are actually compatible with most crypt() implementations. You should be able to use "crypt" to handle them both.> http://wiki.dovecot.org/Authentication/PasswordSchemes seems to indicate > that I have to pick 1, but that is per auth-worker, right? > > So, I created 2 auth workers using 2 dovecot-sql config files specifying > different default encryption schemes and it seems to work. > > Is there any problem with this, other than a small bit of overhead for 2 > queries if the first doesn't hit?Auth worker is actually a bit wrong term to describe two passdb configurations. :) But there should be no problems with a configuration like this anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070414/ac88c3fd/attachment.bin>
Timo Sirainen wrote:> On Fri, 2007-04-13 at 15:04 -0700, Ken Anderson wrote: >> Just upgrading to 1.0.0 and I'm trying to switch from PAM (using >> pam-mysql) to a direct mysql query from dovecot, and I've got both >> md5crypt and crypt passwords in a password db. > > md5crypt and crypt are actually compatible with most crypt() > implementations. You should be able to use "crypt" to handle them both.Works great. Thanks, Ken Anderson Pacific.Net> >> http://wiki.dovecot.org/Authentication/PasswordSchemes seems to indicate >> that I have to pick 1, but that is per auth-worker, right? >> >> So, I created 2 auth workers using 2 dovecot-sql config files specifying >> different default encryption schemes and it seems to work. >> >> Is there any problem with this, other than a small bit of overhead for 2 >> queries if the first doesn't hit? > > Auth worker is actually a bit wrong term to describe two passdb > configurations. :) But there should be no problems with a configuration > like this anyway. >
Reasonably Related Threads
- Postfix/mysql/dovecot - Understanding password encryption
- trouble setting up dovecot on Ubuntu server with mysql backend
- password schemes in dovecot
- HELP: wrinting dovecot-sql.conf to authenticate to an existing database
- Fatal: Unknown scheme: SHA512-CRYPT. On a Mac-mini