Git-Mirrors/haveno
1
0
Fork 0
mirror of https://github.com/haveno-dex/haveno.git synced 2024-12-25 07:19:30 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update external-tor-usage.md

Browse Source
This commit is contained in:
preland 2024-10-29 11:50:56 -05:00 committed by GitHub
parent 10285cd37a
commit 6f05e7bf9f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
docs/external-tor-usage.md
View File

@ -3,47 +3,44 @@
## Setting up Tor: ## Setting up Tor:
### 1. Download and Install Tor ### 1. Download and Install Tor
#### Linux > If you already have Tor, you can skip this step; ensure it has POW support before proceeding.
You can install Tor through your system's package manager (on Debian/Ubuntu: ```apt install tor```; see note 1. below), or directly by going to torproject.org. Note that your package manager's version of tor might be outdated or non-GNU (see note 2. below).
#### MacOS Regardless of platform, the recommended way to download and install Tor is by going to [the Tor Project's website](https://www.torproject.org/download/) and following their instructions.
You can install Tor through Homebrew (```brew install tor```), or directly by going to torproject.org. Note that the Homebrew version of tor might be outdated or non-GNU (see note 2. below). > For best results, ensure that your version of tor matches the one currently used by Haveno. To improve loading times, it is highly recommended to use the GNU build, as it has support for POW. You can check if your build is GNU by running tor --version and looking for a response mentioning GNU.
#### Windows
You can install Tor directly by going to torproject.org.
>1. Tor recommends using their own repository on Debian/Ubuntu, see [here](https://support.torproject.org/apt/tor-deb-repo/).
>2. For best results, ensure that your version of tor matches the one currently used by Haveno. To improve loading times, it is highly recommended to use the GNU build, as it has support for POW. You can check if your build is GNU by running tor --version and looking for a response mentioning GNU.
### 2. Add the following lines to your torrc file: ### 2. Add the following lines to your torrc file:
``` ```
controlPort=9051 controlPort=9051
CookieAuthentication 1 CookieAuthentication 1
CookieAuthFile <path to cookie auth file> CookieAuthFile <tor config path>/control_auth_cookie
``` ```
> The "CookieAuthFile" will not exist until after Tor is ran, so running Tor once will create it if it does not exist. The file's location, while technically arbitrary, should be in a relatively stable and safe place. For example, on Linux it could be placed at ```/etc/tor/control_auth_cookie```, or next to your torrc file. > The "CookieAuthFile" will not exist until after Tor is ran, so running Tor once should create it if it does not exist.
#### The location of your torrc file varies depending on your system: #### Your torrc file is within your tor config path, which varies depending on your system:
#### Linux ##### Linux
```/etc/tor/torrc``` ```/etc/tor/torrc```
#### MacOS ##### MacOS
```/usr/local/etc/tor/torrc``` ```/usr/local/etc/tor/torrc```
#### Windows ##### Windows
```\Browser\TorBrowser\Data\Tor\torrc``` (when using the Tor Browser Bundle) ```\Browser\TorBrowser\Data\Tor\torrc``` (when using the Tor Browser Bundle)
> The above locations are best guesses, and may be incorrect depending on your installation method or platform distribution. In the case that you cannot find the correct directory to place your torrc, tor can be ran in the following format to use a custom torrc: ```tor -f <path to torrc>``` > The above locations are best guesses, and may be incorrect depending on your installation method or platform distribution. In the case that you cannot find the correct directory to place your torrc or you suspect the desired directory is not being used, tor can be ran with a custom torrc: ```tor -f <path to torrc>```
### 3. Stop any currently running tor processes ### 3. Stop any currently running tor processes
#### Linux/MacOS #### Linux/MacOS
```killall tor``` ```killall tor```
#### Windows #### Windows
```Stop-Process -Name tor``` ```Stop-Process -Name tor```
>on Linux/MacOS, it may be wise to also run ```sudo killall tor``` in case the process is owned by root on accident. On systems with multiple concurrent users, properly killing tor might require running ```killall tor``` on all relevant users.
### 4. Start Tor ### 4. Start Tor
```tor``` To start tor, simply run ```tor```, or ```tor -f <path to torrc>``` for a custom configuration.
>On Linux/MacOS, the user running tor must be a member of the "tor" usergroup. >On Linux/MacOS, the user running tor must be a member of the "tor" usergroup.
## Using External Tor with Haveno: ## Using External Tor with Haveno:
Run the Haveno binary with the following extra flags: Run the Haveno binary with the following extra flags:
``` ```
--torControlPort=9051 --torControlCookieFile=<path to cookie auth file> --torControlUseSafeCookieAuth=true --torControlPort=9051 --torControlCookieFile=<tor config path>/control_auth_cookie --torControlUseSafeCookieAuth=true
``` ```
> Replace the ```<path to cookie auth file>``` with the location you specified in step 2. > Replace the ```<tor config path>``` with the location specified in step 2.
> Depending on how your version of Haveno was distributed, you may not have direct access to the Haveno binary. In this case, you should look inside your Haveno distribution for the binary, and then run the binary using the above flags. For example, on MacOS the binary will be located within the app at Haveno.app/Contents/MacOS/Haveno, or something similar. > Depending on how your version of Haveno was distributed, you may not have direct access to the Haveno binary. In this case, you should look inside your Haveno distribution for the binary, and then run the binary using the above flags. For example, on MacOS the binary will be located within the app at Haveno.app/Contents/MacOS/Haveno, or something similar.