Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
Kristijan Savic - ratiokontakt GmbH
ks at ratiokontakt.de
Wed Mar 6 18:16:48 EET 2019
Greetings,
this is less of a bug report or a help request, but we would like to know if
someone can explain the following:
Environment: Centos 7 with Dovecot 2.3.4-2
default_pass_scheme = BLF-CRYPT
password hash in database : BLF-CRYPT
login = works
default_pass_scheme = SHA512 or SHA256-CRYPT
password hash in database : BLF-CRYPT
login = also works
default_pass_scheme = BLF-CRYPT
password hash in database : SHA512-CRYPT
login = does not work
Can someone explain these discrepancies?
--
Kind regards,
Kristijan Savic
--------------------------------------------------------
ratiokontakt GmbH
Biegenhofstr. 13
96103 Hallstadt
Telefon: +49 (0) 951 9 35 35 - 0
Telefax: +49 (0) 951 9 35 35 - 902
Internet: www.ratiokontakt.de
Geschäftsführer: Dr. Nils Kaufmann, Stefan Kraft
Amtsgericht Bamberg - HRB 3757
--------------------------------------------------------
ratiokontakt ist zertifiziert nach DIN ISO/IEC 27001
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <https://dovecot.org/pipermail/dovecot/attachments/20190306/c9d7a8fe/attachment.sig>
More information about the dovecot
mailing list