OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000207f: OpenSSL 1.0.2g-fips 1 Mar 2016; running with 1000207f: OpenSSL 1.0.2g 1 Mar[
running ubuntu 16 and Linux 4.4.0-109-generic Tor 0.3.2.9
Trac: Username: Dbryrtfbcbhgf
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Trac: Username: Dbryrtfbcbhgf Priority: Medium to High Severity: Normal to Major Summary: I keep getting this error to I keep getting this error. "OpenSSL version from headers does not match the version we're running with"
Please don't use priorities to try to get attention for your issues. It doesn't work, and it confuses us when we review tickets. If you want us to look at a ticket, set the version field correctly, and set the milestone field to the next release.
The warning is telling you that your packager compiled tor against the FIPS-certified version of OpenSSL, but you installed the non-FIPS-certified version. This is a slightly weird thing to do, but it is unlikely to cause any issues if the versions are similar enough.
(In this case, they are the same version, with slightly different compilation options.)
If you get weird crashes, that might be why.
Unless you get weird crashes, this is not a bug.
Trac: Milestone: N/Ato Tor: 0.3.2.x-final Resolution: N/Ato not a bug Version: N/Ato Tor: 0.3.2.9 Description: ```
OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000207f: OpenSSL
1.0.2g-fips 1 Mar 2016; running with 1000207f: OpenSSL 1.0.2g 1 Mar[
running ubuntu 16 and Linux 4.4.0-109-generic Tor 0.3.2.9 **to**
OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000207f: OpenSSL 1.0.2g-fips 1 Mar 2016; running with 1000207f: OpenSSL 1.0.2g 1 Mar[
running ubuntu 16 and Linux 4.4.0-109-generic Tor 0.3.2.9 **Status**: new **to** closed **Severity**: Major **to** Normal **Priority**: High **to** Medium
Please don't use priorities to try to get attention for your issues. It doesn't work, and it confuses us when we review tickets. If you want us to look at a ticket, set the version field correctly, and set the milestone field to the next release.
The warning is telling you that your packager compiled tor against the FIPS-certified version of OpenSSL, but you installed the non-FIPS-certified version. This is a slightly weird thing to do, but it is unlikely to cause any issues if the versions are similar enough.
(In this case, they are the same version, with slightly different compilation options.)
If you get weird crashes, that might be why.
Unless you get weird crashes, this is not a bug.
Thank you teor for the explanation. I did not know that I could not use priorities, There is no documentation I could find that shows that I'm not supposed to use it "priorities setting". I will take your recommendations Into consideration in the future when creating tickets.