aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRiccardo Spagni <ric@spagni.net>2015-12-22 10:25:16 +0200
committerRiccardo Spagni <ric@spagni.net>2015-12-22 10:25:20 +0200
commit76837fe5bc87afedcef7e9b600a116cdd2c88da9 (patch)
tree6e530cbdefea2bd4b35b4d6ed42001c837d9b731
parentMerge pull request #547 (diff)
parentREADME.md: fix Tor paragraph to use warptangent's TCP DNS changes (diff)
downloadmonero-76837fe5bc87afedcef7e9b600a116cdd2c88da9.tar.xz
Merge pull request #549
af1da98 README.md: fix Tor paragraph to use warptangent's TCP DNS changes (moneromooo-monero)
-rw-r--r--README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/README.md b/README.md
index 71b9a635e..32485cc7a 100644
--- a/README.md
+++ b/README.md
@@ -174,8 +174,9 @@ See README.i18n
## Using Tor
-While Monero isn't made to integrate with Tor, it can be used wrapped with torsocks, if you add --p2p-bind-ip 127.0.0.1 to the bitmonerod command line.
-Be aware that your DNS use will probably go over clearnet. These come in two flavours: request for checkpoint data, and request for OpenAlias data. The first one is mostly harmless (your ISP can tell you're using monero). The second one leaks information about your transaction recipients, so do not use OpenAlias if you want DNS privacy.
+While Monero isn't made to integrate with Tor, it can be used wrapped with torsocks, if you add --p2p-bind-ip 127.0.0.1 to the bitmonerod command line. You also want to set DNS requests to go over TCP, so they'll be routed through Tor, by setting DNS_PUBLIC=tcp. Example:
+
+DNS_PUBLIC=tcp torsocks bitmonerod --p2p-bind-ip 127.0.0.1
## Using readline