Difference between revisions of "Running Bisq on Tails"

From Bisq Wiki
Jump to navigation Jump to search
(Created page with "[WIP] In order to use Bisq on the Tails OS, a few manual steps are required. == Preparations == * configure a [https://tails.boum.org/doc/first_steps/welcome_screen/adminis...")
 
Line 29: Line 29:
 
do a simple <code>sudo dpkg -i [yourbinaryhere]</code>
 
do a simple <code>sudo dpkg -i [yourbinaryhere]</code>
  
== further configuration needed ==
+
== Configure ==
 +
 
 +
 
  
 
* make authcookie readable:
 
* make authcookie readable:
 
<pre>sudo chmod o+r /var/run/tor/control.authcookie</pre>
 
<pre>sudo chmod o+r /var/run/tor/control.authcookie</pre>
* added iptables rules to connect to nodes:
+
 
 +
* configure <code>onion-grater</code>
 +
<code>wget https://raw.githubusercontent.com/Whonix/onion-grater/master/usr/share/doc/onion-grater-merger/examples/40_bisq.yml</code>
 +
 
 +
 
 +
* In <code>/usr/share/applications/Bisq.desktop</code> replace
 +
<pre>Exec=/opt/Bisq/Bisq</pre>
 +
with
 +
<pre>Exec=/opt/Bisq/Bisq --torControlPort 9052 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth --useTorForBtc=True</pre>
 +
 
 +
 
 +
* TODO
 +
* do we need that in startup args?
 +
<pre>socks5ProxyBtcAddress=127.0.0.1:9050 --socks5ProxyHttpAddress=127.0.0.1:9050</pre>
 +
seems like tails will do that anyways because all traffic from tails goes over tor
 +
* added iptables rules to connect to nodes:
 +
<pre>
 
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8333 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
 
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8333 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
 
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8000 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
 
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8000 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
 
+
</pre>
and started bisq:
+
seems to me that this has been used to allow connecting to seed nodes while using the localhostforp2p (which means there is no tor involved for Bisq at all)
<pre>./Bisq --torControlPort 9052 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth --seedNodes=ef5qnzx6znifo3df.onion:8000,s67qglwhkgkyvr74.onion:8000 --socks5ProxyBtcAddress=127.0.0.1:9050 --socks5ProxyHttpAddress=127.0.0.1:9050 --useTorForBtc=True</pre>
 

Revision as of 11:42, 10 April 2020

[WIP]

In order to use Bisq on the Tails OS, a few manual steps are required.

Preparations

Install

Go to https://github.com/bisq-network/bisq/releases using your Tor Browser and download the Bisq-64bit-[version].deb and .asc files.

You may have to use wget, because curl may not use Tor and therefore is blocked from internet access.

Verify your download

  • wget https://bisq.network/pubkey/[keyid].asc should result in a file [keyid].asc in your working directory
  • import the key to gpg by gpg --import [keyid].asc
  • check the signature with gpg --digest-algo SHA256 --verify [yourbinaryhere]{.asc*,} which should give you something like this

[snip] gpg: Good signature from "Christoph Atteneder... [snip]

Install Bisq

do a simple sudo dpkg -i [yourbinaryhere]

Configure

  • make authcookie readable:
sudo chmod o+r /var/run/tor/control.authcookie
  • configure onion-grater

wget https://raw.githubusercontent.com/Whonix/onion-grater/master/usr/share/doc/onion-grater-merger/examples/40_bisq.yml


  • In /usr/share/applications/Bisq.desktop replace
Exec=/opt/Bisq/Bisq

with

Exec=/opt/Bisq/Bisq --torControlPort 9052 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth --useTorForBtc=True


  • TODO
* do we need that in startup args?
socks5ProxyBtcAddress=127.0.0.1:9050 --socks5ProxyHttpAddress=127.0.0.1:9050

seems like tails will do that anyways because all traffic from tails goes over tor

* added iptables rules to connect to nodes:
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8333 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8000 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq

seems to me that this has been used to allow connecting to seed nodes while using the localhostforp2p (which means there is no tor involved for Bisq at all)