Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tor does not work on Debian Sid (trixie) with OpenSSL 3 #7352

Open
Talkless opened this issue Jan 6, 2025 · 3 comments
Open

Tor does not work on Debian Sid (trixie) with OpenSSL 3 #7352

Talkless opened this issue Jan 6, 2025 · 3 comments

Comments

@Talkless
Copy link

Talkless commented Jan 6, 2025

Description

Tor does not start due to lack of libssl.so.1.1 in Debian Sid (upcomming Trixie):

[ERR] ERROR org.berndpruenster.netlayer.tor.Tor: /home/user/.local/share/Bisq/btc_mainnet/tor/tor: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 

Its 3.3.2:

apt policy libssl3t64
libssl3t64:
  Installed: 3.3.2-2
  Candidate: 3.3.2-2

Using symlink hack /lib/libssl.so.1.1 -> /usr/lib/x86_64-linux-gnu/libssl.so.3 as I did in #2257 does not work due to binary incompatibility:

[ERR] ERROR org.berndpruenster.netlayer.tor.Tor: /home/user/.local/share/Bisq/btc_mainnet/tor/tor: /lib/libssl.so.1.1: version `OPENSSL_1_1_0' not found (required by /home/user/.local/share/Bisq/btc_mainnet/tor/tor

Version

1.9.18

Steps to reproduce

Build 1.9.18 from source and run in current Debian Sid/Testing.

Expected behaviour

Should probably support OpenSSL 3?

Actual behaviour

Does not support OpenSSL 3 and does not start in systems that no longer have OpenSSL 1.x.

Screenshots

Device or machine

amd64 laptop on Debian Sid.

Additional info

@Talkless
Copy link
Author

Talkless commented Jan 6, 2025

As a side question: can't it use local tor node installed in the system via it's SOCKS? Or even use it's control port to create hidden services, etc?

@suddenwhipvapor
Copy link
Contributor

I understand this is not the answer you would like, yet as development efforts are all being spent on bisq2, I do not expect this issue to be tackled. A less ideal workaround would be to run bisq in a debian stable vm

@Talkless
Copy link
Author

My (horrible?) workaround is to download and extract older libssl and libcrypto from Bullseye:

wget -P /tmp/ http://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1w-0+deb11u2_amd64.deb
dpkg -x /tmp/libssl1.1_1.1.1w-0+deb11u2_amd64.deb /tmp/libssl/
sudo cp -v /tmp/libssl/usr/lib/x86_64-linux-gnu/lib* /usr/lib/x86_64-linux-gnu/

Since files are versioned, they Should Not™ make any problems for other software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants