Run ssldump and visit a few https sites and it segfaults. gdb backtrace New TCP connection #141: 192.168.13.100(37367) <-> static.sourceforge.net(443) 141 1 0.2857 (0.2857) C>S Handshake ClientHello Version 3.1 cipher suites Unknown value 0xff Unknown value 0x88 Unknown value 0x87 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA Unknown value 0x84 TLS_RSA_WITH_AES_256_CBC_SHA Unknown value 0x45 Unknown value 0x44 TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA Unknown value 0x96 Unknown value 0x41 TLS_RSA_WITH_RC4_128_MD5 TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA Unknown value 0xfeff TLS_RSA_WITH_3DES_EDE_CBC_SHA compression methods NULL 142 5 0.1997 (0.0427) C>S Handshake ClientKeyExchange 142 6 0.1997 (0.0000) C>S ChangeCipherSpec 142 7 0.1997 (0.0000) C>S Handshake 142 8 0.2772 (0.0774) S>C Handshake Program received signal SIGSEGV, Segmentation fault. 0x4474a606 in vfprintf () from /lib/libc.so.6 (gdb) bt #0 0x4474a606 in vfprintf () from /lib/libc.so.6 #1 0x447f7ad1 in __vfprintf_chk () from /lib/libc.so.6 #2 0x0804fe4a in ?? () #3 0x08050113 in ?? () #4 0x0804cbd0 in ?? () #5 0x0805013b in ?? () #6 0x08050364 in ?? () #7 0x0804d8b4 in ?? () #8 0x0804bcec in ?? () #9 0x0804ad75 in ?? () #10 0x0804affc in ?? () #11 0x448c089d in ?? () from /usr/lib/libpcap.so.1 #12 0x448c3d41 in pcap_loop () from /usr/lib/libpcap.so.1 #13 0x080499b9 in ?? () #14 0x44720413 in __libc_start_main () from /lib/libc.so.6 #15 0x08049be1 in ?? () Backtrace stopped: Not enough registers or memory available to unwind further (gdb)
That backtraces doesn't seem to be really helpful. Can you please install the needed -debuginfo packages and do a "bt full"?
Created attachment 529075 [details] gdb backtrace Sorry about that. gdb backtrace is attached.
ssldump-0.9-0.4.b3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.fc16
ssldump-0.9-0.4.b3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.fc15
ssldump-0.9-0.4.b3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.fc14
ssldump-0.9-0.4.b3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.el6
ssldump-0.9-0.4.b3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.el5
ssldump-0.9-0.4.b3.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/ssldump-0.9-0.4.b3.el4
Package ssldump-0.9-0.4.b3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ssldump-0.9-0.4.b3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14863 then log in and leave karma (feedback).
I'm using Fedora 15. Is it okay to use the F16 build or should I wait till it's available in the updates-testing repository for F15?
ssldump-0.9-0.4.b3.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
ssldump-0.9-0.4.b3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
ssldump-0.9-0.4.b3.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.
ssldump-0.9-0.4.b3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
ssldump-0.9-0.4.b3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
ssldump-0.9-0.4.b3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.