Re: SASL and GSSAPI (ITS#2944)

[sjh@google.com]

On one system:
cyrus-sasl-debuginfo-2.1.17-1
cyrus-sasl-plain-2.1.17-1
cyrus-sasl-2.1.17-1
cyrus-sasl-devel-2.1.17-1
cyrus-sasl-md5-2.1.17-1
cyrus-sasl-gssapi-2.1.17-1
openldap-clients-2.2.5-1
openldap-servers-2.2.5-1
openldap-debuginfo-2.2.5-1
openldap-2.2.5-1
openldap-devel-2.2.5-1



On the other:
cyrus-sasl-2.1.10-4
cyrus-sasl-plain-2.1.10-4
cyrus-sasl-gssapi-2.1.10-4
cyrus-sasl-md5-2.1.10-4
openldap-2.1.22-7gg3
openldap-clients-2.1.22-7gg3
openldap-servers-2.1.22-7gg3


Both have the same problem

But, I don't think it's the same problem as in the cyrus bug report.
All the code to read/write blocks of gssapi encrypted data is in
openldap, but, I must admit, that looking at that code, it all looks
fine to me (it's careful to always break up the calls to encode
the data into chunks of the right size...).


-Seth