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

follow established conventions for Tor integration #1924

Open
adrelanos opened this issue Mar 24, 2024 · 1 comment
Open

follow established conventions for Tor integration #1924

adrelanos opened this issue Mar 24, 2024 · 1 comment
Assignees

Comments

@adrelanos
Copy link

Bisq seems to take quite a unique approach to Tor integration, not following any established conventions. Therefore making things difficult down the line and incompatible with Tor based operating systems such as Whonix and perhaps Tails.

issues:

  • It is currently not possible to use Bisq with an already installed system Tor?
  • Bisq cannot be with a Tor that is already running on a different computer (or virtual machine)?
  • Add Whonix 17 Support #1894

old issues fixed in git:

  • Bisq even used to parse Tor's log file. Just mentioning this to show that invented solutions without looking at the exiting conventions and talking to the Tor community, complex things will be implemented, incompatible, causing later issues, requiring refactoring.

Notes:

What are the conventions? See:

Full disclosure: I am a developer of Whonix.

@sk757a
Copy link

sk757a commented Apr 1, 2024

With the current implementation, it is impossible to connect to the network from countries with restrictions. I need to be able to use my own Tor configuration or a standalone Tor instance.

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

No branches or pull requests

4 participants