From 505542663dc74511172edae669cf03bc3add3f9a Mon Sep 17 00:00:00 2001 From: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com> Date: Mon, 11 May 2020 23:32:38 +0000 Subject: [PATCH] Merge #12384: [Docs] Add version footnote to tor.md (#3473) * 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 \ Tree-SHA512: 439f4ccc3e196011af448b220adf26b0e653ac589bf4cfbbc276c1500c9d08f209c9d6101e4d232857779d9f25164cfb222ed30e3d63de116f9121e6ebde31c3 Signed-off-by: pasta Signed-off-by: Pasta * bitcoin -> Dash Core Signed-off-by: Pasta Co-authored-by: Wladimir J. van der Laan --- doc/tor.md | 23 +++++++++-------------- 1 file changed, 9 insertions(+), 14 deletions(-) diff --git a/doc/tor.md b/doc/tor.md index 2eeb23c3de..fb0481f37c 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -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. @@ -10,8 +9,7 @@ See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#T 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 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 -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 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/ 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 -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 @@ -116,8 +113,7 @@ Note: All these nodes are hosted by masternodehosting.com * 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 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 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. Otherwise it is trivial to link them, which may reduce privacy. Hidden services created automatically (as in section 3) always have only one port