Skip to content

segfaults with HW acceleration

as reported in #tor, Tor 0.1.1.12 (from the RPM) crashes when HW crypto engines are available. OpenSSL was probably at 0.9.7.

Jan 16 11:22:48.845 [notice] Using OpenSSL engine Aep hardware engine support [aep] for RSA
Jan 16 11:22:48.845 [notice] Using OpenSSL engine Aep hardware engine support [aep] for DH
Jan 16 11:22:48.846 [notice] Using OpenSSL engine Aep hardware engine support [aep] for RAND

Core was generated by `tor -f /etc/tor/torrc'.

(gdb) bt
#0 0x00828480 in ?? ()
#1 0x02f5affe in ENGINE_load_aep () from /lib/libcrypto.so.4
legacy/trac#2 (closed) 0x02f5aadb in ENGINE_load_aep () from /lib/libcrypto.so.4
legacy/trac#3 (closed) 0x02f48082 in RSA_blinding_on () from /lib/libcrypto.so.4
legacy/trac#4 (closed) 0x02f460a4 in RSA_PKCS1_SSLeay () from /lib/libcrypto.so.4
legacy/trac#5 (closed) 0x02f46531 in RSA_PKCS1_SSLeay () from /lib/libcrypto.so.4
legacy/trac#6 (closed) 0x02f47e9e in RSA_private_encrypt () from /lib/libcrypto.so.4
legacy/trac#7 (closed) 0x02f486c6 in RSA_sign () from /lib/libcrypto.so.4
legacy/trac#8 (closed) 0x02f75393 in EVP_SignFinal () from /lib/libcrypto.so.4
legacy/trac#9 (closed) 0x02f7de9d in ASN1_item_sign () from /lib/libcrypto.so.4
legacy/trac#10 (closed) 0x02f9c74e in X509_sign () from /lib/libcrypto.so.4
legacy/trac#11 (closed) 0x080b122a in tor_tls_create_certificate ()
legacy/trac#12 (closed) 0x080b14fc in tor_tls_context_new ()
legacy/trac#13 (closed) 0x097ba2f0 in ?? ()
legacy/trac#14 (closed) 0x080ba9cf in command_c_id ()
legacy/trac#15 (closed) 0xbfeea670 in ?? ()
legacy/trac#16 (closed) 0x43cc17af in ?? ()
legacy/trac#17 (closed) 0xffffffff in ?? ()
legacy/trac#18 (closed) 0xbfeea668 in ?? ()
legacy/trac#19 (closed) 0x02f22e1d in CRYPTO_free () from /lib/libcrypto.so.4
Previous frame inner to this frame (corrupt stack?)

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information