Yes I didn't mean the commit was wrong. The problem is MS-AD, but before the
commit it was possible to do LDAP SASL bind over an SSL/TLS connection to AD
if you set min and max SSF below or equal to 128 (doesn't need to be zero).
So it would be nice to have some sort of AD compatibility mode. I
Yes I didn't mean the commit was wrong. The problem is MS-AD, but before the
commit it was possible to do LDAP SASL bind over an SSL/TLS connection to AD
if you set min and max SSF below or equal to 128 (doesn't need to be zero).
So it would be nice to have some sort of AD compatibility mode. I
The workaround proposed by Johnny Westerlund on 2015-05-06
works in cyrus-sasl-2.1.23 but not in the latest version 2.1.26.
Looks like it is this commit that cause the workaround to stop working.
The workaround proposed by Johnny Westerlund on 2015-05-06
works in cyrus-sasl-2.1.23 but not in the latest version 2.1.26.
Looks like it is this commit that cause the workaround to stop working.
