Escape special characters in LDAP filter #27
Conversation
This file contains hidden or 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
RFC 4515 requires * ( ) \ and NUL to be escaped with a backslash followed by the hexadecimal representation of the byte value. https://tools.ietf.org/html/rfc4515#section-3
Owner
|
I'll have a look at this next week. I guess I've just depended on Net::LDAP to handle it. |
Author
|
Net::LDAP has no handling for this, sadly. Net::LDAP::Filter knows how to escape and unescape attribute values in a filter, but the only input form is the filter string, so we must do the escaping ourselves. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
RFC 4515 requires
*()\andNULto be escaped with a backslashfollowed by the hexadecimal representation of the byte value.