diff options
| author | Ross Nicoll <[email protected]> | 2018-01-20 18:35:31 +0000 |
|---|---|---|
| committer | Ross Nicoll <[email protected]> | 2019-03-25 05:36:12 +0000 |
| commit | 731b7a75c2bba4d4ba5a213ca5235ac334a998b0 (patch) | |
| tree | 99ab6f8e5a3bc0efa17b14fb6d69d623dd2edf12 /doc/tor.md | |
| parent | Rename and update man pages (#1451) (diff) | |
| download | discoin-731b7a75c2bba4d4ba5a213ca5235ac334a998b0.tar.xz discoin-731b7a75c2bba4d4ba5a213ca5235ac334a998b0.zip | |
Update documentation to match 1.10 (#1436)
Diffstat (limited to 'doc/tor.md')
| -rw-r--r-- | doc/tor.md | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/tor.md b/doc/tor.md index a05979fca..092674649 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -1,22 +1,22 @@ -TOR SUPPORT IN BITCOIN -====================== +TOR SUPPORT IN DOGECOIN +======================= -It is possible to run Bitcoin as a Tor hidden service, and connect to such services. +It is possible to run Dogecoin as a Tor hidden service, and connect to such services. 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 configure Tor. -1. Run bitcoin behind a Tor proxy +1. Run Dogecoin behind a Tor proxy --------------------------------- -The first step is running Bitcoin behind a Tor proxy. This will already make all +The first step is running Dogecoin behind a Tor proxy. This will already make all outgoing connections be anonymized, but more is possible. -proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy server will be used to try to reach .onion addresses as well. - -onion=ip:port Set the proxy server to use for tor hidden services. You do not + -onion=ip:port Set the proxy server to use for Tor hidden services. You do not need to set this if it's the same as -proxy. You can use -noonion to explicitly disable access to hidden service. @@ -31,27 +31,27 @@ outgoing connections be anonymized, but more is possible. In a typical situation, this suffices to run behind a Tor proxy: - ./bitcoin -proxy=127.0.0.1:9050 + ./dogecoin -proxy=127.0.0.1:9050 -2. Run a bitcoin hidden server +2. Run a Dogecoin 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): - HiddenServiceDir /var/lib/tor/bitcoin-service/ - HiddenServicePort 8333 127.0.0.1:8333 - HiddenServicePort 18333 127.0.0.1:18333 + HiddenServiceDir /var/lib/tor/dogecoin-service/ + HiddenServicePort 22556 127.0.0.1:22556 + HiddenServicePort 44556 127.0.0.1:44556 The directory can be different of course, but (both) port numbers should be equal to -your bitcoind's P2P listen port (8333 by default). +your dogecoind's P2P listen port (22556 by default). - -externalip=X You can tell bitcoin about its publicly reachable address using + -externalip=X You can tell Dogecoin about its publicly reachable address using this option, and this can be a .onion address. Given the above configuration, you can find your onion address in - /var/lib/tor/bitcoin-service/hostname. Onion addresses are given + /var/lib/tor/dogecoin-service/hostname. Onion addresses are given preference for your node to advertise itself with, for connections coming from unroutable addresses (such as 127.0.0.1, where the Tor proxy typically runs). @@ -68,7 +68,7 @@ your bitcoind's P2P listen port (8333 by default). In a typical situation, where you're only reachable via Tor, this should suffice: - ./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen + ./dogecoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen (obviously, replace the Onion address with your own). It should be noted that you still listen on all devices and another node could establish a clearnet connection, when knowing @@ -79,14 +79,14 @@ your address. To mitigate this, additionally bind the address of your Tor proxy: If you don't care too much about hiding your node, and want to be reachable on IPv4 as well, use `discover` instead: - ./bitcoind ... -discover + ./dogecoind ... -discover -and open port 8333 on your firewall (or use -upnp). +and open port 22556 on your firewall (or use -upnp). If you only want to use Tor to reach onion addresses, but not use it as a proxy for normal IPv4/IPv6 communication, use: - ./bitcoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover + ./dogecoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover 3. Automatically listen on Tor -------------------------------- |