similar to: Using pgsql with 'cram-md5 auth' and 'hmac-md5 scheme'

Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high

Hi, I'm just in the middle of setting up dovecot to serve IMAPS -- Actually I've finished apart from one thing: CRAM-MD5 passwords. I'm using SQL as a backend for the password storage, and I don't want to store the passwords in plaintext. I've also configured dovecot to be rather restrictive when it comes to authentication methods (only CRAM-MD5 is allowed). To generate the

Hi all, Got a question on configuring dovecot, I'm still new at this so I might be doing this all wrong. I want dovecot to authenticate the mail client using CRAM-MD5 so I've setup the config in dovecot.conf: auth default { mechanisms = cram-md5 passdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf args = /etc/dovecot/dovecot-sql.conf

$ dovecotpw -p testpass {HMAC-MD5}fe8522268d91e485ccac8f36800e4fa6b10363e2a371cfa61731109b450906cd I wonder if the prefix 'HMAC-MD5' is the correct notation here. According to RFC2104 an HMAC is calculated as follows: H(K XOR opad, H(K XOR ipad, text)) where H is the cryptographic hash function (MD5 in this case). Therefore the result has to be a 128 bit string, which is obviously not

Platform is Solaris 8 on a 280R. I'm setting up a new installation of Dovecot, and I ran into some troubles that I've partly tracked down. I setup auth/user dbs with LDAP initially, and things worked well. Passwords are stored as "{crypt}zxcv..." in LDAP. I setup SQL, and began getting this: dovecot: Jan 23 16:37:47 Error: child 8718 (auth-worker) killed with signal 11

Hi to all! I?m writing a python module (python+sqlalchemy) to manage user and domain configuration on my system (I hope to get a CLI tool, a Web app and even a native Mac app, via PyObjc, from my lib). I?m implementing password crypto, but I have some problem in generating CRAM-MD5 password, dovecot style. I?ve found an old discussion on this mailing list and a piece of Perl that works, but I need

I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?

The idea of salted hash algorithms is to generate a different hash even if the same text is entered. That can be easily seen with dovecotpw: using NON-salted SHA256, same hash is generated for a given password [root at correio ~]# dovecotpw -s SHA256 -p 123 {SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM= [root at correio ~]# dovecotpw -s SHA256 -p 123

Hello list, our users are authenticated against ldap-server. anything works fine... dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured but now we want to use secure passwords and not only plain over ssl. so we configured dovecot to use cram-md5 and configured the ldap-server with CRAM-MD5 passwords. as client we used thunderbird 2.0 and a

After upgrading my dovecot installation about a month ago, I have started seeing "Requested CRAM-MD5 scheme, but we have only MD5-CRYPT" message from dovecot in my logs. Any help in finding and correcting the cause will be greatly appreciated. --Richard

Hi, based on the recent discussion by Bill Cole and Douglas Willcocks I've quickly put together a PHP script which generates MD5 'contexts' for Dovecot's password files: http://www.noerenberg.de/hajo/pub/dovecot_hmacmd5.php.txt The script has not been tested extensively, so use it on your own risk :) Most of the code has been shamelessly stolen from various sources.

Hi, please apply the following patch to dovecotpw. Without this, it will be unusable on powerpc and (maybe) other architectures where the char is unsigned by default. --- dovecot-1.0/src/util/dovecotpw.c (revisione 2066) +++ dovecot-1.0.new/src/util/dovecotpw.c (copia locale) @@ -40,7 +40,7 @@ const char *user = NULL; char *scheme = NULL; char *plaintext = NULL; - char ch; +

I've decided that having users supply cleartext passwords for me to encrypt and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The idea is that users supply an already-encrypted password. Most of the users can fetch their login password from /etc/shadow on their own computer. Wiki page http://wiki.dovecot.org/Authentication/PasswordSchemes indicates that scheme name

Hello, Is this the proper place to suggest an enhancement for the stock dovecot package ? The enhancement would be the following: For the time being, the dovecotpw utility offers a standardised way to interactively encode a user password in a certain scheme, say: dovecotpw -s CRYPT Enter new passord: Re-enter new password: etc. Given a *valid* /etc/imap.passwd file (passwd-file

Hi again, I`m a bit confused how to store a SSHA256 password in the database and I can`t find any information in the wiki. Do I have to store the SHA256 hash and the salt separately (what would the password_query be like in this way) or just the final SSHA256 hash? Regards Patrick

I config postfix+mysql+dovecot for SASL SMTP autentication. It works if set: default_pass_scheme = PLAIN and store plain-text password in mysql I'm change default_pass_scheme = PLAIN with default_pass_scheme = PLAIN-MD5 an store password in mysql with md5('passwd') and dovecotpw -s PLAIN-MD5 -p test {PLAIN-MD5} and md5("test") = 098f6bcd4621d373cade4e832627b4f6 but

Hello, I have a working installation of Dovecot, which use passwd-file for both users and passwords databases. My setup uses CRAM-MD5 for the authentification mechanism and the password in my passwd-file was stored encoded with HMAC-MD5. Now, I want to use Postgresql to replace those passwd-files. So I make the necessary change in my dovecot.conf file : =========================================

/etc/dovecot.conf: auth default { mechanisms=plain login cram-md5 passdb { #.............. Windows Live Mail: CRAM-MD5 authentication failed. This could be due to a lack of memory on your system. Your IMAP command could not be sent to the server, due to non-network errors. This could, for example, indicate a lack of memory on your system. Configuration: Account: Sheltoncomputers

I am switching from a fedora/postfix/mysql/couriermail/squirrelmail to Centos/.../dovecot/roundcubemail and adding postfixadmin to the mix. My tutorial before was an earlier version (on F14) of: http://www.howtoforge.com/virtual-users-and-domains-with-postfix-courier-mysql-and-squirrelmail-centos-6.2-x86_64 Now I am using

We have a plethora of accounts for which we would like to enable CRAM-MD5 but their passwords are stored as MD5 hashes. Is there anything we can do? Can we take a linux MD5 hashed password (e.g. $1$fac330ee$wd6Tll...) and convert it to dovecot's CRAM-MD5 format (e.g. {CRAM-MD5}b3f297...)? Thanks!