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 (JIRA)" <ji...@apache.org> on 2013/05/06 22:32:16 UTC

[jira] [Updated] (TS-1779) Crash using ssl_ca_name

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

James Peach updated TS-1779:
----------------------------

    Summary: Crash using ssl_ca_name  (was: Crash using SNI and ssl_ca_name)
    
> Crash using ssl_ca_name
> -----------------------
>
>                 Key: TS-1779
>                 URL: https://issues.apache.org/jira/browse/TS-1779
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>            Reporter: Rodney
>            Assignee: James Peach
>              Labels: A
>             Fix For: 3.2.6
>
>
> When I add 'ssl_ca_name' to include a chain cert CA the traffic server fails to start with a core dump. It seems to be okay if I just have one entry in 'ssl_multicert.config' file but as soon as I use SNI the traffic server will not start with a core dump.
> This witnessed on 3.2.0 and currently 3.2.4 with Debian Squeeze.
> Example entries:
> ssl_cert_name=my1.crt ssl_key_name=my1.key ssl_ca_name=my1CA.crt
> ssl_cert_name=my2.crt ssl_key_name=my2.key ssl_ca_name=my2CA.crt
> #Default
> dest_ip=* ssl_cert_name=my1.crt ssl_key_name=my1.key ssl_ca_name=my1CA.crt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira