-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add Whonix 17 Support #1894
Comments
Issue 1) Above issue will most likely be resolved in next Bisq 2 release thanks to #1914. Issue 2) But now I am running into a different issue. Using Bisq 2 from git.
In Whonix Bisq documentation chapter Tor over Tor Prevention we currently suggest:
The Something similar worked for Bisq 1. But even that is no longer possible with Bisq 2. The most useful change would be honor environment variable
Issue 3) I was able to workaround Issue 2) by initially letting Bisq create file, then stopping Bisq, then deleting file But Bisq is still waiting for some Tor log file which it cannot find.
Maybe deprecation of parsing Tor's log file in #1914 was incomplete? |
running into similar issue on Ubuntu:
built from jdk 11 |
@polishboi This is fixed for next release. |
We don't know the SOCKS5 port when we're using to a running Tor daemon. This change is needed to support external Tor instances. Ref: bisq-network#1894
Tails and Whonix use onion-grater to filter dangerous Tor control protocol commands. Therefore, users need to enable the Bisq onion-grater profile on those operating systems. We should detect filtered commands and help users to setup their operating system. Ref: bisq-network#1894
Should be fixed with v2.0.4. It is available as pre-release at https://github.com/bisq-network/bisq2/releases/tag/v2.0.4 (if you enable notifications for pre-release in the preferences you get the update notification). |
- Remove deprecated SETEVENTS command - Add missing ADD_ONION pattern and replacement - Fix HS_DESC UPLOAD pattern and replacement - Add missing HS_DESC FAILED pattern and replacement Ref: bisq-network/bisq2#1894
We re-implemented the Tor Control Protocol in Java to add Whonix/onion-grater support. I opened a PR in the onion-grater repository to update the Bisq 2 onion-grater profile. The next Bisq 2 release will fully support Whonix. |
Yes, I can. Due to @alvasw PR on #2286 and PR on Whonix/onion-grater#11, I will be able to test only in 2.0.5. |
Here is a PR implementing support for connecting to an external Tor process: #3046 |
Hello and thank you for developing Bisq V2.
I had to create the dummy tor binary:
mkdir -p /home/user/.local/share/Bisq2/tor ## Sudo necessary to avoid package overwriting the binary sudo touch /home/user/.local/share/Bisq2/tor/tor chmod +x /home/user/.local/share/Bisq2/tor/tor
Torrc of Bisqv2 (unmodified by me):
Using the command:
/opt/bisq2/bin/Bisq\ 2 --torControlPort=9051 --torControlPassword=notrequired --socks5ProxyBtcAddress=127.0.0.1:9050 --useTorForBtc=true
So, is there a command line option to skip creating the tor log file?
I don't see to find the command line help option
Tor bootstrap always stops at 24% and I never see it reach onion-grater on the Whonix-Gateway.
The text was updated successfully, but these errors were encountered: