I am running =net-misc/tor-0.2.7.6. After its daemon crashed, I found this in /var/log/messages: OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000205f: OpenSSL 1.0.2e 3 Dec 2015; running with 1000207f: OpenSSL 1.0.2g 1 Mar 2016). After I rebuilt tor, this message no longer appeared. This should be done automatically by Portage when OpenSSL is upgraded.
(In reply to Pastafarianist from comment #0) > I am running =net-misc/tor-0.2.7.6. After its daemon crashed, I found this > in /var/log/messages: > > OpenSSL version from headers does not match the version we're running with. > If you get weird crashes, that might be why. (Compiled with 1000205f: > OpenSSL 1.0.2e 3 Dec 2015; running with 1000207f: OpenSSL 1.0.2g 1 Mar > 2016). > > After I rebuilt tor, this message no longer appeared. > > This should be done automatically by Portage when OpenSSL is upgraded. Did this happen only once?
(In reply to Anthony Basile from comment #1) > Did this happen only once? Yes. Tor crashed, I looked in the logs, found this, and it never crashed again.
(In reply to Pastafarianist from comment #2) > (In reply to Anthony Basile from comment #1) > > Did this happen only once? > > Yes. Tor crashed, I looked in the logs, found this, and it never crashed > again. we can leave this bug open to see if we get more reports but right now i think the message is a false positive. in gentoo we slot openssl so that we can trigger rebuilds if we there is an api/abi change. if there's no abi/api change then there should be no reason to rebuild tor against the new openssl. that doesn't mean there might not be some subtle abi change that we missed and therefore we got the slotting wrong, but i don't have enough information from your report to determine that.
