Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x509name: Correct inverted return for #eql? #100

Closed
wants to merge 1 commit into from
Closed

x509name: Correct inverted return for #eql? #100

wants to merge 1 commit into from

Conversation

adrienthebo
Copy link

Commit 34e7fe3 introduced a regression that inverted the return value
of OpenSSL::X509::Name#eql?; this commit fixes Bug #13170 and restores the
original semantics.

Reference: https://bugs.ruby-lang.org/issues/13170

Commit 34e7fe3 introduced a regression that inverted the return value
of OpenSSL::X509::Name#eql?; this commit fixes Bug #13170 and restores the
original semantics.

Reference: https://bugs.ruby-lang.org/issues/13170
@rhenium
Copy link
Member

rhenium commented Jan 31, 2017

Thank you for reporting. I commited an identical patch just a few days ago: 4ccaf25

@rhenium rhenium closed this Jan 31, 2017
@adrienthebo adrienthebo deleted the openssl-x509name-eql branch February 1, 2017 00:01
shawnferry pushed a commit to shawnferry/puppet that referenced this pull request Jun 30, 2017
Commit [34e7fe3][regression] of ruby/openssl negated the behavior of
`OpenSSL::X509::Name#eql?`, which broke our spec tests.
In contrast `OpenSSL::X509::Name#== continues to work as expected and
the use of `#eql?` is uncommon; this commit bypasses the issue entirely.

[regression]: ruby/openssl@34e7fe3#diff-8621484175a9fd7841e498512cb2944f
[bugfix]: ruby/openssl#100
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants