You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "James Peach (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/28 06:08:41 UTC

[jira] [Resolved] (TS-1135) support wildcard certificates for ServerNameIndication (SNI)

     [ https://issues.apache.org/jira/browse/TS-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Peach resolved TS-1135.
-----------------------------

    Resolution: Fixed

bb5402304c30b8b2107e1f845bb301f5a6a9b022 TS-1135: Remove std::distance to make Solaris happy
ce8fb7ef1bc9a6e351ef160d51036e03cb7892c4 TS-1135: Fix signed/unsigned warning
0dcad6eaf692e6acee68685c08788bc42e8e15b3 TS-1135: index wildcard certificates for ServerNameIndication
313c224d66fd12800612986b0ad0c58b25a1392a TS-1135: add some const qualifiers to DFA::match()
9c1958ab49e3cd6a8f4fec785a033a204ea222bb TS-1135: minor Trie and Queue fixes
687fdbfee6d47c6d4d81f9458d69d23311f6f35d TS-1135: move Trie.h to libts

                
> support wildcard certificates for ServerNameIndication (SNI)
> ------------------------------------------------------------
>
>                 Key: TS-1135
>                 URL: https://issues.apache.org/jira/browse/TS-1135
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: SSL
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 3.1.4
>
>
> The ServerNameIndication support added in TS-472 doesn't handle wildcard certificates. We need to add certificate parsing support to detect wildcard certificates and then (if there is not an exact match) choose the certificate with the longest wildcard match.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira