https://bugs.winehq.org/show_bug.cgi?id=55304
--- Comment #1 from Hans Leidekker hans@meelstraat.net --- I have replaced QueryContextAttributesA(SECPKG_ATTR_KEY_INFO) with QueryContextAttributesA(SECPKG_ATTR_SESSION_KEY) after implementing the attribute for Kerberos and NTLM.
SSF is used by ldap_int_sasl_bind() to determine if the SASL security layer should be used at all. This page documents it as representing the key size for values > 1:
https://docs.oracle.com/cd/E19120-01/open.solaris/819-2145/sasl.intro-44/ind...
I don't understand why the trailer size depends on the server since we have always depended on a constant trailer size. Is that because of a difference between Samba and AD?
I can find references for Windows changing from 12000 max token size to 48000 but not 48256. Where does it come from?
Also note that your changes to sasl_decode() and sasl_encode() break NTLM.