https://bugzilla.novell.com/show_bug.cgi?id=897113 https://bugzilla.novell.com/show_bug.cgi?id=897113#c0 Summary: tor is built with/against previous openssl-1.0.1h and with a problematic configuration option Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lars.edman@bredband.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 I run an updated openSUSE 12.3 x86_64 with openssl-1.0.1i-1.64.1.x86_64 Current tor-0.2.4.23-2.12.1.x86_64 from openSUSE-update seems to be built against OpenSSL-1.0.1h and leaves the following warning msg: sep 14 12:01:58.258 [Varning] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000108f: OpenSSL 1.0.1h 5 Jun 2014; running with 1000109f: OpenSSL 1.0.1i 6 Aug 2014). I have experienced the same after upgrading openssl to -1.0.1i in my Slackware server and got rid of the weird crashes through rebuilding tor against openssl-1.0.1i. -Will you do the same and update the tor.rpm? (I myself got problems trying to build it from source). Besides: The tor.log reports an other warning msg concerning your config: 14 12:01:58.258 [Varning] Tor was compiled with the --enable-bufferevents option. This is still experimental, and might cause strange bugs. If you want a more stable Tor, be sure to build without --enable-bufferevents. I can report that my current tor show strange bugs. It would be nice if you made an update of tor-0.2.4.23 built against openssl-1.0.1i and without --enable-bufferevents! Reproducible: Always Steps to Reproduce: 1. Start current tor-0.2.4.23-2.12.1.x86_64 with logging enabled 2. Read tor-log 3. (The crashes does not always come, but after a longer or shorter period) Actual Results: The warning msgs in the tor log always appear. The crashes does not come immediately, but after a longer or shorter period. The "weird bugs" described above appear from time to time, reported in the log, sometimes first after an hour or more. One "weird bug" example: sep 14 13:05:01.526 [Warning] Something tried to close an or_connection_t without going through channels at src/or/connection.c:3228 Expected Results: none of the events described under Actual Results About the severity: I can't call the bug severe, but every time I use tor as a client and it crashes: Of course I loose data. I would say it's an update miss: You should know that every time you update openssl you have to rebuild and update tor as well. Regards -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.