On 11/18/18 7:13 PM, Quanah Gibson-Mount wrote: > --On Sunday, November 18, 2018 5:48 PM +0000 [email protected] wrote: >> Sounds like this is an issue for the Cyrus SASL project. Their plugin is >> returning a SASL_BADPROT error code on all failures, instead of a more >> meaningful code like SASL_BADAUTH. > > I opened <https://github.com/cyrusimap/cyrus-sasl/issues/545>
Thanks. > since they're working on getting the 2.1.27 release out anytime now > and this should likely be fixed as a part of that release. It seems they cut the release yesterday: ftp://ftp.cyrusimap.org/cyrus-sasl/ Nevermind, I'm not using SASL password mechs for anything serious. Just stumbled across this while implementing a regression test for bad password in ldap0 module which explicitly checks that invalidCredentials(49) is returned. Ciao, Michael.
