Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas

[Kristijan Savic - ratiokontakt GmbH]

> You could configure default scheme as CRYPT. It covers these all. Otherwise
> you need to make sure passwords have {SCHEME} prefix when it differs from
> default or oddities occur. ---

Thank you for the tip with CRYPT.

Is there any explanation for this behaviour though?

Why are BCRYPT hashes accepted when default_pass_scheme is set to SHA512-CRYPT 
and not vice versa?  Is this normal?

-- 
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/20190307/dd761157/attachment.sig>