diff options
| author | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2015-12-19 19:12:38 +0000 |
|---|---|---|
| committer | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2015-12-19 19:12:38 +0000 |
| commit | af1da980f095d049953b9324b65bae67063c9f7f (patch) | |
| tree | ac4c1623d067c74ef8ee5f792fac9dbb9f39f64a | |
| parent | Merge pull request #544 (diff) | |
| download | monero-af1da980f095d049953b9324b65bae67063c9f7f.tar.xz | |
README.md: fix Tor paragraph to use warptangent's TCP DNS changes
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -174,6 +174,7 @@ 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 |