sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-25 03:52:49 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge #12384: [Docs] Add version footnote to tor.md (#3473)

Browse Source 
* Merge #12384: [Docs] Add version footnote to tor.md

39d2911 [Docs] Add version footnote to tor.md (Damian Williamson)

Pull request description:

  [Docs] Add version footnote to tor.md

  Added note to section 2, part -edits to `/etc/tor/torrc`- indicating this is only required for Tor version 0.2.7.0 and older, since section 3 states it is valid for Tor version 0.2.7.1 and newer. Added ref link from section 2 version footnote to section 3. Re-styled headings to work on GitHub -alternate heading style markup creation issue with numbered headings and thus headings and automatic heading links are broken-

  Ref: [Issue# 12376](https://github.com/bitcoin/bitcoin/issues/12376)

  Signed-off-by: Damian Williamson \<willtech@live.com.au\>

Tree-SHA512: 439f4ccc3e196011af448b220adf26b0e653ac589bf4cfbbc276c1500c9d08f209c9d6101e4d232857779d9f25164cfb222ed30e3d63de116f9121e6ebde31c3
Signed-off-by: pasta <pasta@dashboost.org>
Signed-off-by: Pasta <pasta@dashboost.org>

* bitcoin -> Dash Core

Signed-off-by: Pasta <pasta@dashboost.org>

Co-authored-by: Wladimir J. van der Laan <laanwj@gmail.com>
This commit is contained in:
PastaPastaPasta 2020-05-11 23:32:38 +00:00 committed by GitHub
parent 1c20160933
commit 505542663d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/tor.md
View File

@ -1,5 +1,4 @@
TOR SUPPORT IN DASH CORE # TOR SUPPORT IN DASH CORE
=======================
It is possible to run Dash Core as a Tor hidden service, and connect to such services. It is possible to run Dash Core as a Tor hidden service, and connect to such services.
@ -10,8 +9,7 @@ See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#T
for how to properly configure Tor. for how to properly configure Tor.
1. Run Dash Core behind a Tor proxy ## 1. Run Dash Core behind a Tor proxy
----------------------------------
The first step is running Dash Core behind a Tor proxy. This will already make all The first step is running Dash Core behind a Tor proxy. This will already make all
outgoing connections be anonymized, but more is possible. outgoing connections be anonymized, but more is possible.
@ -44,12 +42,12 @@ In a typical situation, this suffices to run behind a Tor proxy:
./dashd -proxy=127.0.0.1:9050 ./dashd -proxy=127.0.0.1:9050
2. Run a Dash Core hidden server ## 2. Run a Dash Core hidden server
-------------------------------
If you configure your Tor system accordingly, it is possible to make your node also If you configure your Tor system accordingly, it is possible to make your node also
reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
config file): config file): *Needed for Tor version 0.2.7.0 and older versions of Tor only. For newer
versions of Tor see [Section 4](#4-automatically-listen-on-tor).*
HiddenServiceDir /var/lib/tor/dashcore-service/ HiddenServiceDir /var/lib/tor/dashcore-service/
HiddenServicePort 9999 127.0.0.1:9999 HiddenServicePort 9999 127.0.0.1:9999
@ -99,8 +97,7 @@ for normal IPv4/IPv6 communication, use:
./dashd -onion=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -discover ./dashd -onion=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -discover
3. List of known Dash Core Tor relays ## 3. List of known Dash Core Tor relays
------------------------------------
Note: All these nodes are hosted by masternodehosting.com Note: All these nodes are hosted by masternodehosting.com
@ -116,8 +113,7 @@ Note: All these nodes are hosted by masternodehosting.com
* fijy6aikzxfea54i.onion * fijy6aikzxfea54i.onion
4. Automatically listen on Tor ## 4. Automatically listen on Tor
--------------------------------
Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket
API, to create and destroy 'ephemeral' hidden services programmatically. API, to create and destroy 'ephemeral' hidden services programmatically.
@ -143,10 +139,9 @@ which has the appropriate permissions. An alternative authentication method is t
of the `-torpassword` flag and a `hash-password` which can be enabled and specified in of the `-torpassword` flag and a `hash-password` which can be enabled and specified in
Tor configuration. Tor configuration.
5. Privacy recommendations ## 5. Privacy recommendations
---------------------------
- Do not add anything but bitcoin ports to the hidden service created in section 2. - Do not add anything but Dash Core ports to the hidden service created in section 2.
If you run a web service too, create a new hidden service for that. If you run a web service too, create a new hidden service for that.
Otherwise it is trivial to link them, which may reduce privacy. Hidden Otherwise it is trivial to link them, which may reduce privacy. Hidden
services created automatically (as in section 3) always have only one port services created automatically (as in section 3) always have only one port