Skip to content

configure detects wrong openssl version

Summary

configure detects wrong openssl version

Steps to reproduce:

No matter --enable-static-openssl is set or not

  1. ./configure

What is the current bug behavior?

configure:9946: Now, we'll look for OpenSSL >= 1.0.1 no
configure:10286: checking for OpenSSL >= 3.0.0 yes
  1. tor

Tor 0.4.5.9 running on.......... OpenSSL 1.1.1k

What is the expected behavior?

Environment

  • Which version of Tor are you using? Run tor --version to get the version if you are unsure.

Tor 0.4.5.9

  • Which operating system are you using? For example:

Debian GNU/Linux

  • Which installation method did you use? Distribution package (apt, pkg, homebrew), from source tarball, from Git, etc.

apt, tarball, Git

Relevant logs and/or screenshots

configure:9946: Now, we'll look for OpenSSL >= 1.0.1
configure:9967: checking for openssl directory
configure:10254: result: (none)
configure:10286: checking for OpenSSL >= 3.0.0
conftest.c:57:2: error: #error "you_have_version_3"
   57 | #error "you_have_version_3"
      |  ^~~~~
configure:10304: $? = 1
| #if !defined(LIBRESSL_VERSION_NUMBER) && OPENSSL_VERSION_NUMBER <= 0x30000000L
| #error "you_have_version_3"
configure:10308: result: yes
configure:10316: checking for OpenSSL < 1.0.1
configure:10334: $? = 0
configure:10335: result: no
configure:10362: $? = 0
configure:10369: checking for significant mismatch between openssl headers and libraries
configure:10411: result: no
configure: Now, we'll look for OpenSSL >= 1.0.1
checking for openssl directory... /ucrt64/lib
checking whether we need extra options to link openssl... (none)
checking for OpenSSL >= 3.0.0... yes
checking for OpenSSL < 1.0.1... no
checking for significant mismatch between openssl headers and libraries... no

Possible fixes

Edited by pseudonymisaTor
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information