[
https://issues.apache.org/jira/browse/TS-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311417#comment-15311417
]
Michael Sokolnicki edited comment on TS-4480 at 6/2/16 12:06 AM:
-----------------------------------------------------------------
I uploaded a diff containing our approach to this fix, it is based on commit
1385f5287f8cc2bf63271e656a5cfb011d021dc6. I don't have a github account at the
moment, so I thought this would be easier. Let me know if you really need it as
a PR.
was (Author: msokolnicki):
I uploaded a diff containing our approach to this fix, it is based on commit
1385f5287f8cc2bf63271e656a5cfb011d021dc6. I don't have a github account at the
moment, so I thought this would be easier.
> Wildcards in certificates should only match one level
> -----------------------------------------------------
>
> Key: TS-4480
> URL: https://issues.apache.org/jira/browse/TS-4480
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SSL
> Reporter: Michael Sokolnicki
> Fix For: 7.0.0
>
> Attachments: current_patch.diff
>
>
> According to RFC 6125 section 6.4.3:
> {quote}
> If the wildcard character is the only character of the left-most label in the
> presented identifier, the client SHOULD NOT compare against anything but the
> left-most label of the reference identifier (e.g., *.example.com would match
> foo.example.com but not bar.foo.example.com or example.com).
> {quote}
> In the current implementation, certificates are searched for in a trie, and
> the longest match is returned, but there is no check if that match complies
> with the above rule. This causes invalid certs to be returned and SLL errors
> in the browser (in Firefox, we get SSL_ERROR_BAD_CERT_DOMAIN).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
