[ 
https://issues.apache.org/jira/browse/TS-4480?focusedWorklogId=29044&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29044
 ]

ASF GitHub Bot logged work on TS-4480:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Sep/16 15:45
            Start Date: 14/Sep/16 15:45
    Worklog Time Spent: 10m 
      Work Description: GitHub user shinrich opened a pull request:

    https://github.com/apache/trafficserver/pull/1019

    TS-4480: Fix memory leak with wildcard cert match fix

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shinrich/trafficserver ts-4480-2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/1019.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1019
    
----

----


Issue Time Tracking
-------------------

    Worklog Id:     (was: 29044)
    Time Spent: 3h 20m  (was: 3h 10m)

> 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
>            Assignee: Susan Hinrichs
>             Fix For: 7.0.0
>
>         Attachments: current_patch.diff
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to