Receiving mail with checked STARTTLS in SSL tab crashes sylpheed. Simple debuging revealed a seg fault in SSL_connect (ssl.c:106). I also tried latest openssl-0.9.6h same there. (gdb) bt full #0 0x00000000 in ?? () No symbol table info available. #1 0x4044b404 in ssl3_send_alert () from /lib/libssl.so.2 No symbol table info available. #2 0x4044a595 in ssl3_get_record () from /lib/libssl.so.2 No symbol table info available. #3 0x4044ac94 in ssl3_read_bytes () from /lib/libssl.so.2 No symbol table info available. #4 0x4044bc50 in ssl3_get_message () from /lib/libssl.so.2 No symbol table info available. #5 0x40445fd2 in ssl3_get_server_hello () from /lib/libssl.so.2 No symbol table info available. #6 0x40445860 in ssl3_connect () from /lib/libssl.so.2 No symbol table info available. #7 0x40450020 in SSL_connect () from /lib/libssl.so.2 No symbol table info available. #8 0x08140349 in ssl_init_socket_with_method (sockinfo=0x8620770, method=SSL_METHOD_TLSv1) at ssl.c:106 method = 135777161 server_cert = (X509 *) 0x817cb89 ssl = (SSL *) 0x8624500 #9 0x080f1060 in pop3_stls_recv (sock=0x8620770, data=0x861c640) at pop.c:130 sock = (SockInfo *) 0x8620770 cheers Oliver
This looks like a NULL value in a function pointer. The only line in the ssl source that could cause this segfault is: desc=s->method->ssl3_enc->alert_value(desc); These are all static values that are not changed by sylpheed as far as i know. Is this bug reproduceable? If yes can you try to reproduce it with a openssl library with debugging symbols? Maybe this is a bug in OpenSSL. If you get the error with debugging symbols it would be good if you could print *s->method->ssl3_enc with gdb.
*** Bug 49 has been marked as a duplicate of this bug. ***
I'd like to test it a bit (just added starttls to my smtp server and it works), Oliver, could you give me your pop server's name (or ip) ? I don't need a valid login. Cheers Colin
Using Sylpheed 0.8.11claws156 and OpenSSL 0.9.7b STARTTLS works without problems for me.