-
Notifications
You must be signed in to change notification settings - Fork 184
Stricter hostname verification #10
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
Conversation
|
The Disallowing wildcards on TLDs is recommended by ICANN: |
lib/openssl/ssl.rb
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a comment here to indicate the reasoning for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
I'd prefer we nodoc these functions (for now) to avoid promoting them as public api |
|
@zzak my last commit makes the existing test suite pass (sans the unrelated memory leak error) |
|
I'd call this finished for a first pass |
|
Can you squash your commits please? |
4188c09 to
ea9a6f8
Compare
|
Squashed |
lib/openssl/ssl.rb
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't strict enough.
>> san_component = "abc*bcd"
>> domain_component = "abcd"
>> parts = san_component.split("*", -1)
>> domain_component.start_with?(parts[0]) && domain_component.end_with?(parts[1])
=> true|
Sans the issue above, LGTM. More tests, though? |
ea9a6f8 to
a67b7ef
Compare
a67b7ef to
75c94a1
Compare
|
Will reopen with the in-repo branch |
|
Reopened as #12 |
This change implements hostname verification more in-line with RFC 6125.
Additionally it eliminates the use of regexes when verifying hostnames, opting for simple string comparisons instead.