This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Make SSL Cert lookup case-insensitive#3331
Merged
dangogh merged 2 commits intoapache:masterfrom Feb 20, 2019
Merged
Conversation
added 2 commits
February 15, 2019 15:14
Set SSL certificate key names to lower case Set requested SNI to lower case
Set SSL certificate key names to lower case Set requested SNI to lower case
Contributor
|
Can one of the admins verify this patch? |
|
@ajschmidt I've tested this PR successfully. 2 of 2 manual tests of this PR are successful. This PR is ready to be merged. Testing environment:
Tests:
Results: Test1 - Verify GET request containing mixed case FQDN in URL returns the correct certificate for demo1 delivery service: Test2 - Verify Raw SNI mixed case FQDN in TLS client_hello returns the correct certificate for demo1 DS: |
ghost
approved these changes
Feb 20, 2019
Member
|
add to whitelist |
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
ajschmidt
added a commit
to ajschmidt/trafficcontrol
that referenced
this pull request
Mar 14, 2019
* Fix case-sensitive SSL cert lookup * Set SSL certificate key names to lower case * Set requested SNI to lower case (cherry picked from commit 6504e7f)
dg4prez
pushed a commit
that referenced
this pull request
Mar 15, 2019
* Make SSL Cert lookup case-insensitive (#3331) * Fix case-sensitive SSL cert lookup * Set SSL certificate key names to lower case * Set requested SNI to lower case (cherry picked from commit 6504e7f) * Add SSL Certificate Validation to Traffic Router (#3380) * updated tr docker config so it would work * added start and stop scripts for TR docker containers * fixed bug in Tomcat which wasn't unregistering old SslHostConfigs * Added validation checks of SSL certs while being loaded by CertificateRegistry * Changed error message for Certificate Expired * Corrected a parsing error in certificate validation checking Set the startup/shutdown scripts for the TR docker container to executable * Corrected some code formatting and one NullPointerException * Added info to CHANGELOG.md (cherry picked from commit 0d2560d) * Corrected CHANGELOG * Another CHANGELOG correction
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Which issue is fixed by this PR? If not related to an existing issue, what does this PR do?
OpenSSL is performing an exact match between the requested SNI and the lookup keys associated with SSL Certificates. Since FQDNs are not case sensitive this is inappropriate and sometimes causes misses on the certificate lookup. TR incorrectly returns the default certificate in these cases. This PR is a workaround for this issues by:
Fixes #(replace_this_text_with_issue_number)
Which TC components are affected by this PR?
What is the best way to verify this PR? Please include manual steps or automated tests.
(If no tests are part of this PR, please provide explanation as to why no tests are included.)
The easiest way to test this PR is to start up a local instance of TR by running TrafficRouterStart and configuring it to point at an existing Traffic Ops instance which is configured with at least one SSL Cert and a matching Delivery Service which is SSL enabled. Any existing non-production environment should do. Run a couple of 'curl' commands:
should perform an SSL handshake and return a certificate for domain myds.mycdn.mycompany.com
should perform an SSL handshake and return the same certificate as in #1.
Of course you have to replace myds, mycdn and mycompany with the fqdn for your delivery service.
Check all that apply