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/05 05:40:17 UTC
[jira] [Comment Edited] (TS-1779) Crash using SNI and ssl_ca_name
[ https://issues.apache.org/jira/browse/TS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649256#comment-13649256 ]
James Peach edited comment on TS-1779 at 5/5/13 3:38 AM:
---------------------------------------------------------
Here's the backtrace from traffic.out:
{code}
*** glibc detected *** /usr/local/trafficserver/bin/traffic_server: double free or corruption (fasttop): 0x000000000307fdb0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x71e16)[0x2aaaad2b1e16]
/lib/libc.so.6(cfree+0x6c)[0x2aaaad2b6b8c]
/usr/local/trafficserver/bin/traffic_server(_ZN13SSLCertLookup10buildTableEv+0x32f)[0x6ad37f]
/usr/local/trafficserver/bin/traffic_server(_ZN13SSLCertLookup4initEP15SslConfigParams+0x1d)[0x6ad3fd]
/usr/local/trafficserver/bin/traffic_server(_ZN15SSLNetProcessor11reconfigureEv+0x6d)[0x688aad]
/usr/local/trafficserver/bin/traffic_server(_ZN15SSLNetProcessor5startEi+0x20)[0x688af0]
/usr/local/trafficserver/bin/traffic_server(main+0x10fa)[0x4cde9a]
/lib/libc.so.6(__libc_start_main+0xfd)[0x2aaaad25ec8d]
/usr/local/trafficserver/bin/traffic_server[0x488429]
{code}
was (Author: jamespeach):
Here's the backtrace from traffic.out:
*** glibc detected *** /usr/local/trafficserver/bin/traffic_server: double free or corruption (fasttop): 0x000000000307fdb0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x71e16)[0x2aaaad2b1e16]
/lib/libc.so.6(cfree+0x6c)[0x2aaaad2b6b8c]
/usr/local/trafficserver/bin/traffic_server(_ZN13SSLCertLookup10buildTableEv+0x32f)[0x6ad37f]
/usr/local/trafficserver/bin/traffic_server(_ZN13SSLCertLookup4initEP15SslConfigParams+0x1d)[0x6ad3fd]
/usr/local/trafficserver/bin/traffic_server(_ZN15SSLNetProcessor11reconfigureEv+0x6d)[0x688aad]
/usr/local/trafficserver/bin/traffic_server(_ZN15SSLNetProcessor5startEi+0x20)[0x688af0]
/usr/local/trafficserver/bin/traffic_server(main+0x10fa)[0x4cde9a]
/lib/libc.so.6(__libc_start_main+0xfd)[0x2aaaad25ec8d]
/usr/local/trafficserver/bin/traffic_server[0x488429]
> Crash using SNI and 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.3.3
>
>
> 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