Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  1. TOR SUPPORT IN BITCOIN
  2. ======================
  3. It is possible to run Bitcoin as a Tor hidden service, and connect to such services.
  4. The following assumes you have a Tor proxy running on port 9050. Many distributions
  5. default to having a SOCKS proxy listening on port 9050, but others may not.
  6. In particular, the Tor Browser Bundle defaults to listening on a random port. See
  7. https://www.torproject.org/docs/faq.html.en#TBBSocksPort for how to properly
  8. configure Tor.
  9. 1. Run bitcoin behind a Tor proxy
  10. ---------------------------------
  11. The first step is running Bitcoin behind a Tor proxy. This will already make all
  12. outgoing connections be anonimized, but more is possible.
  13. -socks=5 SOCKS5 supports connecting-to-hostname, which can be used instead
  14. of doing a (leaking) local DNS lookup. SOCKS5 is the default,
  15. but SOCKS4 does not support this. (SOCKS4a does, but isn't
  16. implemented).
  17. -proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy
  18. server will be used to try to reach .onion addresses as well.
  19. -tor=ip:port Set the proxy server to use for tor hidden services. You do not
  20. need to set this if it's the same as -proxy. You can use -notor
  21. to explicitly disable access to hidden service.
  22. -dnsseed DNS seeds are not resolved directly when a SOCKS5 proxy server is
  23. set. Rather, a short-lived proxy connection to the dns seed
  24. hostname is attempted, and peer addresses are requested.
  25. -listen When using -proxy, listening is disabled by default. If you want
  26. to run a hidden service (see next section), you'll need to enable
  27. it explicitly.
  28. -connect=X When behing a Tor proxy, you can specify .onion addresses instead
  29. -addnode=X of IP addresses or hostnames in these parameters. It requires
  30. -seednode=X SOCKS5. In Tor mode, such addresses can also be exchanged with
  31. other P2P nodes.
  32. In a typical situation, this suffices to run behind a Tor proxy:
  33. ./bitcoin -proxy=127.0.0.1:9050
  34. 2. Run a bitcoin hidden server
  35. ------------------------------
  36. If you configure your Tor system accordingly, it is possible to make your node also
  37. reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
  38. config file):
  39. HiddenServiceDir /var/lib/tor/bitcoin-service/
  40. HiddenServicePort 8333 127.0.0.1:8333
  41. The directory can be different of course, but (both) 8333's should be equal to your
  42. bitcoind's P2P listen port (8333 by default).
  43. -externalip=X You can tell bitcoin about its publically reachable address using
  44. this option, and this can be a .onion address. Given the above
  45. configuration, you can find your onion address in
  46. /var/lib/tor/bitcoin-service/hostname. Onion addresses are given
  47. preference for your node to advertize itself with, for connections
  48. coming from unroutable addresses (such as 127.0.0.1, where the
  49. Tor proxy typically runs).
  50. -listen You'll need to enable listening for incoming connections, as this
  51. is off by default behind a proxy.
  52. -discover When -externalip is specified, no attempt is made to discover local
  53. IPv4 or IPv6 addresses. If you want to run a dual stack, reachable
  54. from both Tor and IPv4 (or IPv6), you'll need to either pass your
  55. other addresses using -externalip, or explicitly enable -discover.
  56. Note that both addresses of a dual-stack system may be easily
  57. linkable using traffic analysis.
  58. In a typical situation, where you're only reachable via Tor, this should suffice:
  59. ./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
  60. (obviously replace the Onion address with your own). If you don't care too much
  61. about hiding your node, and want to be reachable on IPv4 as well, additionally
  62. specify:
  63. ./bitcoind ... -discover
  64. and open port 8333 on your firewall (or use -upnp).
  65. If you only want to use Tor to reach onion addresses, but not use it as a proxy
  66. for normal IPv4/IPv6 communication, use:
  67. ./bitcoin -tor=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover