Skip to content

Commit c5f7efe

Browse files
committed
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](bitcoin/bitcoin#12376) Signed-off-by: Damian Williamson \<[email protected]\> Tree-SHA512: 439f4ccc3e196011af448b220adf26b0e653ac589bf4cfbbc276c1500c9d08f209c9d6101e4d232857779d9f25164cfb222ed30e3d63de116f9121e6ebde31c3
2 parents a024a18 + 39d2911 commit c5f7efe

File tree

1 file changed

+7
-11
lines changed

1 file changed

+7
-11
lines changed

doc/tor.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,12 @@
1-
TOR SUPPORT IN BITCOIN
2-
======================
1+
# TOR SUPPORT IN BITCOIN
32

43
It is possible to run Bitcoin as a Tor hidden service, and connect to such services.
54

65
The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on port 9150. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort) for how to properly
76
configure Tor.
87

98

10-
1. Run bitcoin behind a Tor proxy
11-
---------------------------------
9+
## 1. Run bitcoin behind a Tor proxy
1210

1311
The first step is running Bitcoin behind a Tor proxy. This will already make all
1412
outgoing connections be anonymized, but more is possible.
@@ -34,12 +32,12 @@ In a typical situation, this suffices to run behind a Tor proxy:
3432
./bitcoind -proxy=127.0.0.1:9050
3533

3634

37-
2. Run a bitcoin hidden server
38-
------------------------------
35+
## 2. Run a bitcoin hidden server
3936

4037
If you configure your Tor system accordingly, it is possible to make your node also
4138
reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
42-
config file):
39+
config file): *Needed for Tor version 0.2.7.0 and older versions of Tor only. For newer
40+
versions of Tor see [Section 3](#3-automatically-listen-on-tor).*
4341

4442
HiddenServiceDir /var/lib/tor/bitcoin-service/
4543
HiddenServicePort 8333 127.0.0.1:8333
@@ -88,8 +86,7 @@ for normal IPv4/IPv6 communication, use:
8886

8987
./bitcoind -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
9088

91-
3. Automatically listen on Tor
92-
--------------------------------
89+
## 3. Automatically listen on Tor
9390

9491
Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket
9592
API, to create and destroy 'ephemeral' hidden services programmatically.
@@ -115,8 +112,7 @@ which has the appropriate permissions. An alternative authentication method is t
115112
of the `-torpassword` flag and a `hash-password` which can be enabled and specified in
116113
Tor configuration.
117114

118-
4. Privacy recommendations
119-
---------------------------
115+
## 4. Privacy recommendations
120116

121117
- Do not add anything but bitcoin ports to the hidden service created in section 2.
122118
If you run a web service too, create a new hidden service for that.

0 commit comments

Comments
 (0)