Active Directory fixes for alternate encoding RFC4514#324
Open
cmdrclueless wants to merge 4 commits intoruby-ldap:masterfrom
Open
Active Directory fixes for alternate encoding RFC4514#324cmdrclueless wants to merge 4 commits intoruby-ldap:masterfrom
cmdrclueless wants to merge 4 commits intoruby-ldap:masterfrom
Conversation
Merge upstream master (ruby-ldap/ruby-net-ldap)
This reverts commit 019f2aa.
Member
|
Hi @cmdrclueless, thanks for the contribution! Would you be open to taking a pass at implementing tests to demonstrate the expected behavior? |
Contributor
Author
|
If time permits, it is totally up to my employer as the fix was made for
work issues. My free time is already allocated for other projects. I made
the fix for production work and it's in the field so it may be quite a
while.
…On Mon, Nov 18, 2019 at 3:07 PM Matt Todd ***@***.***> wrote:
Hi @cmdrclueless <https://github.com/cmdrclueless>, thanks for the
contribution! Would you be open to taking a pass at implementing tests to
demonstrate the expected behavior?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#324?email_source=notifications&email_token=AABHDKR6XJTSQVPJUMRPMH3QULYY5A5CNFSM4H7XM3U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEELXYEA#issuecomment-555187216>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHDKREE24AJEWMSCCTFATQULYY5ANCNFSM4H7XM3UQ>
.
--
/* insert witty comment here */
|
Member
|
@cmdrclueless do you have a few moments to attempt to write some tests for this? Thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
As part of RFC4514 section 2.4, it's permissible to prefix some characters with the backslash (
\) symbol instead of using the standard format of\xxwherexxis the hexadecimal code for the character in question. This was exposed when a group in Active Directory (AD) was created with a#symbol.Consider the DN
CN=#Supers,DC=foo,DC=bar,DC=com. AD sends this asCN=\#Supers,DC=foo,DC=bar,DC=com, which is an alternative format according to the spec. However the#symbol is hex code 23. This mean the standardized form via the spec should result inCN=\23Supers,DC=foo,DC=bar,DC=com. Unfortunately during testing AD will return the record, if and only if, the alternative format is used.The relevant section of the RFC for this change follows