tor 0.2.2.32 crashes with SIGSEGV on SSL_CIPHER_get_name
When running in daemon mode as a relay, tor crashes with a SIGSEV in in libssl.
Here the stack trace:
#0 0x40168b00 in SSL_CIPHER_get_name () from /lib/libssl.so.1.0.0
#1 0x000bdbb4 in tor_tls_client_is_using_v2_ciphers (ssl=<value optimized out>, address=0x3a0ed8 "[scrubbed]") at tortls.c:866
#2 0x000bde9c in tor_tls_handshake (tls=0x39ea38) at tortls.c:1294
#3 0x00077d98 in connection_tls_continue_handshake (conn=0x39f608) at connection_or.c:920
#4 0x0006e72c in connection_handle_read (conn=0x39f608) at connection.c:2610
#5 0x0001136c in conn_read_callback (fd=<value optimized out>, event=0, _conn=0x401765bc) at main.c:514
#6 0x401018a4 in event_base_loop () from /opt/lib/libevent-2.0.so.5
#7 0x0000e7b8 in do_main_loop () at main.c:1564
#8 0x0000ea70 in tor_main (argc=1, argv=<value optimized out>) at main.c:2226
#9 0x403159a0 in __libc_start_main () from /lib/libc.so.6
#10 0x0000d388 in _start ()
Plattform is a Synology DS211j: Linux 2.6.32.12 #1748 (moved) Wed Jun 29 11:44:24 CST 2011 armv5tel GNU/Linux synology_88f6281_211j
Client-only operation works fine.
Trac:
Username: monochromec