search for: md5_verify

'afternoon list! I use mysql as userdb, which contains two type of password schemes: DES and MD5-CRYPT. I read there : http://wiki.dovecot.org/Authentication/PasswordSchemes that both are supported by dovecot. Unfortunately, dovecot keeps saying: Not a valid MD5-CRYPT or PLAIN-MD5 password when looking for a user with DES encrypted password. Is dovecot able to recognize password

...17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): query: SELECT name AS user, pass AS password FROM users WHERE name='Teacher1' Mar 11 16:17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): Password mismatch Mar 11 16:17:54 SSiS dovecot: auth-worker(default): md5_verify(Teacher1): Not a valid MD5-CRYPT or PLAIN-MD5 password Mar 11 16:17:54 SSiS dovecot: auth-worker(default): Invalid OTP data in passdb Mar 11 16:17:54 SSiS dovecot: auth-worker(default): Invalid OTP data in passdb Mar 11 16:17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): CRYPT(Tea...

...16 02:55:37 auth: Debug: sql(dino at abc.it,xxxx): query: SELECT '{SSHA512.HEX}' || password as password FROM mailboxes WHERE fullusername='dino at abc.it' Apr 16 02:55:37 auth: Info: sql(dino at abc.it,xxxx): Password mismatch (given password: dino) Apr 16 02:55:37 auth: Error: md5_verify(dino at abc.it): Not a valid MD5-CRYPT or PLAIN-MD5 password Apr 16 02:55:37 auth: Warning: Invalid OTP data in passdb Apr 16 02:55:37 auth: Warning: Invalid OTP data in passdb Apr 16 02:55:37 auth: Debug: sql(dino at abc.it,xxxx): SSHA512.HEX(dino) != 'd449914d83c85a786bcde7114b3dfdb24a651c2...

...mail dovecot: auth-worker: Debug: vpopmail(wschoeller at htl-perg.ac.at,10.114.57.11): lookup user=wschoeller domain=htl-perg.ac.at Nov 28 18:43:15 mail dovecot: auth-worker: vpopmail(wschoeller at htl-perg.ac.at,10.114.57.11): Password mismatch Nov 28 18:43:15 mail dovecot: auth-worker: Error: md5_verify(wschoeller at htl-perg.ac.at): Not a valid MD5-CRYPT or PLAIN-MD5 password Nov 28 18:43:15 mail dovecot: auth-worker: Error: smd5_verify(wschoeller at htl-perg.ac.at): SMD5 password too short Nov 28 18:43:15 mail dovecot: auth-worker: Error: ssha_verify(wschoeller at htl-perg.ac.at): SSHA passwo...

Hi, I have a current auth database using mysql with a "password" column in plain text. The config has "default_pass_scheme = PLAIN" specified In preparation for a more adaptable system I changed a password entry from "asdf" to "{PLAIN}asdf", but now auth fails. Works fine if I change it back to just "asdf". (I don't believe it's a

I am testing the version on FreeBSD 7.3-PRELEASE (I doubt it's the issue) and I am having a problem with pop3. Here is what I see in the log when I attempt to connect to port 110: Feb 22 18:15:03 master: Warning: SIGHUP received - reloading configuration Feb 22 18:15:08 pop3-login: Panic: file login-settings.c: line 216 (login_settings_read): assertion failed: (input.roots[count] == NULL) Feb

...ntext)) == 0; +} + +static const char *rpa_generate(const char *plaintext, + const char *user __attr_unused__) +{ + return password_generate_rpa(plaintext); +} + static const struct password_scheme default_schemes[] = { { "CRYPT", crypt_verify, crypt_generate }, { "MD5", md5_verify, md5_generate }, @@ -439,6 +451,7 @@ static const struct password_scheme defa { "LDAP-MD5", ldap_md5_verify, ldap_md5_generate }, { "LANMAN", lm_verify, lm_generate }, { "NTLM", ntlm_verify, ntlm_generate }, + { "RPA", rpa_verify, rpa_generate }, { NU...