Search K
Appearance
Appearance
Digest-MD5 has two things that make it special and which can cause problems:
For these and other reasons Digest-MD5 has been obsoleted (RFC 6331) by SCRAM (RFC 5802).
Realms are an integral part of Digest-MD5. You will need to specify realms you want to advertise to the client in the config file: auth_realms = example.com another.example.com foo
.
The realms don't have to be domains. All listed realms are presented to the client and it can select to use one of them. Some clients always use the first realm. Some clients use your domain name, whenever given more than one realm to choose from. Even if this was NOT one of the choices you provided (KMail, others?). In both cases the user never sees the advertised realms.
WARNING
Any settings that modify the username before the passdb lookup (e.g. auth_default_domain
) will not work with Digest-MD5 password scheme, because the password hash was calculated using the unmodified username. Any username modification will result in hash mismatch.
Password must be stored in either cleartext or with DIGEST-MD5 scheme. See password schemes.
The Digest is the MD5 sum of the string "user:realm:password". For example, if you want to log in as user
with password pass
and the realm should be example.com
(usually not provided by the user, see above), create the digest with:
$ echo -n "user:example.com:pass" | md5sum c19c4c6e32f9d8026b26ba77c21fb8eb -
And save it as: user@example.com:c19c4c6e32f9d8026b26ba77c21fb8eb
.
Note that if you're using DIGEST-MD5 scheme to store the passwords, you can't change the users' names or realms in any way or the authentication will fail because the MD5 sums don't match. Also not that this is different from what Apache does with HTTP AUTH Digest. There it would be user:example.com:c19c4c6e32f9d8026b26ba77c21fb8eb
and is created with htdigest
.
You can use imtest
from Cyrus SASL library to test an IMAP connection:
# With realm:
imtest -a user -r example.com
# Without realm:
imtest -a user@example.com