You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/04 00:08:12 UTC

[jira] [Commented] (TS-4180) support for serving multiple intermediate cert chains

    [ https://issues.apache.org/jira/browse/TS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269712#comment-15269712 ] 

ASF GitHub Bot commented on TS-4180:
------------------------------------

Github user shinrich commented on the pull request:

    https://github.com/apache/trafficserver/pull/578#issuecomment-216679391
  
    I'll plan on working with @jacksontj at the summit next week to get the TSQA and openssl version issue figured out.


> support for serving multiple intermediate cert chains
> -----------------------------------------------------
>
>                 Key: TS-4180
>                 URL: https://issues.apache.org/jira/browse/TS-4180
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: SSL
>            Reporter: Scott Beardsley
>            Assignee: Susan Hinrichs
>              Labels: yahoo
>             Fix For: 6.2.0
>
>
> We would like to serve two different intermediate certificate chains for RSA certs and ECDSA certs. Today they are required to be in the same chain. It seems the best way would be to modify "ssl_ca_name" (or proxy.config.ssl.CA.cert.path) to support a comma-delimited list of intermediate files.
> Bonus points if ATS validates that the intermediate chain matches the cert being served (and spits out an error if there is a mismatch)!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)