Correctly handle GSSAPI SASL negotiated max buffer size as per RFC4752 #1156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ThePirateWhoSmellsOfSunflowers
added a commit
to ThePirateWhoSmellsOfSunflowers/ldap3
that referenced
this pull request
Aug 21, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds code to correctly handle GSSAPI SASL negotiated max buffer size as per RFC4752.
As 0 was sent as the proposed max client buffer size (it should only be 0 if no security layers are configured), Samba would fail with error "gensec_gssapi_unwrap: WRAPPED data is larger than SASL negotiated maximum size".