[
https://issues.apache.org/jira/browse/TS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664038#comment-13664038
]
ASF subversion and git services commented on TS-1779:
-----------------------------------------------------
Commit 22d96a7e4c09d6325b871b320712411000ee76e1 in branch refs/heads/3.2.x from
[~i.galic]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=22d96a7 ]
[TS-1779] Crash when using ssl_ca_name
Patch https://issues.apache.org/jira/secure/attachment/12584296/TS-1779.patch
Test/review: jpeach, zwoop, igalic
backport: igalic
> 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.5
>
> Attachments: TS-1779.patch
>
>
> 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
