As I reported here: kernel tried to execute NX-protected page - exploit attempt? https://github.com/minipli/linux-unofficial_grsec/issues/20#issuecomment-350208705 (find the OpenSSL no-match headers tor log lines near bottom) but it's also about crashes I've had earlier/later, same issues page, but numbers legacy/trac#13, legacy/trac#17, legacy/trac#18, legacy/trac#19, and legacy/trac#21, all my crashes vanished once I disabled tor. Can you pls look up those crashes and confirm if the reason is as I suspect (from same log, just earlier, that line repeated for weeks :) ... ouch!): Dec 07 04:25:47.000 [notice] Tor 0.2.9.12 (git-2b1e823d7bc05a37) opening new log file. Dec 07 04:25:47.859 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1010006f: OpenSSL 1.1.0f 25 May 2017; running with 1010007f: OpenSSL 1.1.0g 2 Nov 2017). Dec 07 04:25:47.885 [notice] Tor 0.2.9.12 (git-2b1e823d7bc05a37) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0g and Zlib 1.2.8. I know this is about package maintainance, but if I got the right cause here, can you pls. direct us where to look for explanation, more information how this come about. Thank you! **Trac**: **Username**: miroR