neobytes/doc/tor.md

134 lines
5.9 KiB
Markdown
Raw Normal View History

2024-02-05 23:00:22 +01:00
TOR SUPPORT IN NEOBYTES CORE
============================
2024-12-16 19:40:22 +01:00
It is possible to run Neobytes Core as a Tor hidden service, and connect to such services.
2015-03-04 21:26:44 +01:00
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 a random
port. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort)
2015-02-22 21:39:26 +01:00
for how to properly configure Tor.
2024-12-16 19:40:22 +01:00
1. Run Neobytes Core behind a Tor proxy
2024-02-05 23:00:22 +01:00
---------------------------------------
2024-12-16 19:40:22 +01:00
The first step is running Neobytes Core 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
need to set this if it's the same as -proxy. You can use -noonion
to explicitly disable access to hidden service.
-listen When using -proxy, listening is disabled by default. If you want
to run a hidden service (see next section), you'll need to enable
it explicitly.
-connect=X When behind a Tor proxy, you can specify .onion addresses instead
-addnode=X of IP addresses or hostnames in these parameters. It requires
-seednode=X SOCKS5. In Tor mode, such addresses can also be exchanged with
other P2P nodes.
2015-03-01 22:48:32 +01:00
-onlynet=tor Only connect to .onion nodes and drop IPv4/6 connections.
An example how to start the client if the Tor proxy is running on local host on
port 9050 and only allows .onion nodes to connect:
2024-02-05 23:00:22 +01:00
./neobytesd -onion=127.0.0.1:9050 -onlynet=tor -listen=0 -addnode=ssapp53tmftyjmjb.onion
2015-03-01 22:48:32 +01:00
In a typical situation, this suffices to run behind a Tor proxy:
2024-02-05 23:00:22 +01:00
./neobytesd -proxy=127.0.0.1:9050
2024-12-16 19:40:22 +01:00
2. Run a Neobytes Core hidden server
2024-02-05 23:00:22 +01:00
------------------------------------
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):
2024-12-16 19:40:22 +01:00
HiddenServiceDir /var/lib/tor/neobytes-service/
HiddenServicePort 1428 127.0.0.1:1428
HiddenServicePort 11428 127.0.0.1:11428
The directory can be different of course, but (both) port numbers should be equal to
2024-12-16 19:40:22 +01:00
your neobytesd's P2P listen port (1428 by default).
2024-12-16 19:40:22 +01:00
-externalip=X You can tell Neobytes Core 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
2024-12-16 19:40:22 +01:00
/var/lib/tor/neobytes-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).
-listen You'll need to enable listening for incoming connections, as this
is off by default behind a proxy.
-discover When -externalip is specified, no attempt is made to discover local
IPv4 or IPv6 addresses. If you want to run a dual stack, reachable
from both Tor and IPv4 (or IPv6), you'll need to either pass your
other addresses using -externalip, or explicitly enable -discover.
Note that both addresses of a dual-stack system may be easily
linkable using traffic analysis.
In a typical situation, where you're only reachable via Tor, this should suffice:
2024-02-05 23:00:22 +01:00
./neobytesd -proxy=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.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
your address. To mitigate this, additionally bind the address of your Tor proxy:
2024-02-05 23:00:22 +01:00
./neobytesd ... -bind=127.0.0.1
If you don't care too much about hiding your node, and want to be reachable on IPv4
as well, use `discover` instead:
2024-02-05 23:00:22 +01:00
./neobytesd ... -discover
2024-12-16 19:40:22 +01:00
and open port 1428 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:
2024-02-05 23:00:22 +01:00
./neobytesd -onion=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -discover
2015-03-01 22:48:32 +01:00
2024-12-16 19:40:22 +01:00
3. List of known Neobytes Core Tor relays
2024-02-05 23:00:22 +01:00
-----------------------------------------
2015-03-01 22:48:32 +01:00
2015-09-23 22:46:31 +02:00
* [darkcoinie7ghp67.onion](http://darkcoinie7ghp67.onion/)
2015-03-02 00:50:18 +01:00
* [drktalkwaybgxnoq.onion](http://drktalkwaybgxnoq.onion/)
2015-03-04 21:26:44 +01:00
* [drkcoinooditvool.onion](http://drkcoinooditvool.onion/)
* [darkcoxbtzggpmcc.onion](http://darkcoxbtzggpmcc.onion/)
2015-03-01 22:48:32 +01:00
* [ssapp53tmftyjmjb.onion](http://ssapp53tmftyjmjb.onion/)
2015-03-04 21:26:44 +01:00
* [j2dfl3cwxyxpbc7s.onion](http://j2dfl3cwxyxpbc7s.onion/)
* [vf6d2mxpuhh2cbxt.onion](http://vf6d2mxpuhh2cbxt.onion/)
2015-09-23 22:46:31 +02:00
* [rj24sicr6i4vsnkv.onion](http://rj24sicr6i4vsnkv.onion/)
* [wrwx2dy7jyh32o53.onion](http://wrwx2dy7jyh32o53.onion/)
* [f5ekot4ajkbe23gt.onion](http://f5ekot4ajkbe23gt.onion/)
* [dshtord4mqvgzqev.onion](http://dshtord4mqvgzqev.onion/)
4. Automatically listen on Tor
--------------------------------
Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket
API, to create and destroy 'ephemeral' hidden services programmatically.
2024-12-16 19:40:22 +01:00
Neobytes Core has been updated to make use of this.
This means that if Tor is running (and proper authorization is available),
2024-12-16 19:40:22 +01:00
Neobytes Core automatically creates a hidden service to listen on, without
manual configuration. This will positively affect the number of available
.onion nodes.
2024-12-16 19:40:22 +01:00
This new feature is enabled by default if Neobytes Core is listening, and
a connection to Tor can be made. It can be configured with the `-listenonion`,
`-torcontrol` and `-torpassword` settings. To show verbose debugging
information, pass `-debug=tor`.