2020-11-12 12:40:52 +01:00
|
|
|
## Fully supported hashing methods
|
2020-11-12 10:20:00 +01:00
|
|
|
|
|
|
|
|
The most current mailcow fully supports the following hashing methods.
|
|
|
|
|
The default hashing method is written in bold:
|
|
|
|
|
|
|
|
|
|
- **BLF-CRYPT**
|
2020-12-07 07:53:16 +01:00
|
|
|
- SSHA
|
2020-11-12 10:20:00 +01:00
|
|
|
- SSHA256
|
|
|
|
|
- SSHA512
|
|
|
|
|
|
|
|
|
|
The methods above can be used in `mailcow.conf` as `MAILCOW_PASS_SCHEME` value.
|
|
|
|
|
|
|
|
|
|
## Read-only hashing methods
|
|
|
|
|
|
|
|
|
|
The following methods are supported **read only**.
|
|
|
|
|
|
2021-02-11 09:48:42 +01:00
|
|
|
- ARGON2I
|
|
|
|
|
- ARGON2ID
|
|
|
|
|
- CLEAR
|
|
|
|
|
- CLEARTEXT
|
|
|
|
|
- CRYPT
|
|
|
|
|
- DES-CRYPT
|
|
|
|
|
- LDAP-MD5
|
|
|
|
|
- MD5
|
2020-11-12 10:20:00 +01:00
|
|
|
- MD5-CRYPT
|
2021-02-11 09:48:42 +01:00
|
|
|
- PBKDF2
|
|
|
|
|
- PLAIN
|
|
|
|
|
- PLAIN-MD4
|
2020-11-12 10:20:00 +01:00
|
|
|
- PLAIN-MD5
|
2021-02-11 09:48:42 +01:00
|
|
|
- PLAIN-TRUNC
|
|
|
|
|
- SHA
|
|
|
|
|
- SHA1
|
|
|
|
|
- SHA256
|
|
|
|
|
- SHA256-CRYPT
|
|
|
|
|
- SHA512
|
2020-11-12 10:20:00 +01:00
|
|
|
- SHA512-CRYPT
|
2021-02-11 09:48:42 +01:00
|
|
|
- SMD5
|
2020-11-12 10:20:00 +01:00
|
|
|
|
|
|
|
|
That means mailcow is able to verify users with a hash like `{PLAIN-MD5}1a1dc91c907325c69271ddf0c944bc72` from the database.
|
|
|
|
|
|
|
|
|
|
The value of `MAILCOW_PASS_SCHEME` will _always_ be used to encrypt new passwords.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
> I changed the password hashes in the "mailbox" SQL table and cannot login.
|
|
|
|
|
|
|
|
|
|
A "view" needs to be updated. You can trigger this by restarting sogo-mailcow: `docker-compose restart sogo-mailcow`
|
