From 1894fb92847e8f4289df444a945958a0416f58f9 Mon Sep 17 00:00:00 2001 From: emdee Date: Fri, 28 Oct 2022 10:52:12 +0000 Subject: [PATCH] AddingAnOnionService --- AddingAnOnionService.md | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/AddingAnOnionService.md b/AddingAnOnionService.md index 758d1e6..c385558 100644 --- a/AddingAnOnionService.md +++ b/AddingAnOnionService.md @@ -7,15 +7,15 @@ number of nodes. This is already happening in places like Iran. It would help if all the BS node operators could also run a Tor client (not exit node), in addition to running their node. There are no risks -to the BS operator from running a Tor client (not exit node), and the -overhead in negligible. The onion server is a 127.0.0.1 service, so -cannot be seen by your ISP. The BS service is on the opennet anyway -so an onion is just another access method. So we get dozens of Tor -onion nodes running quickly, we could test out running Tox *in* Tor -using Hidden Services. If the Tox nodebase was improved to serve BS -nodes, it would be much more resilient. I'm assuming the adversaries -cannot block .onion addresses within Tor, which I think is a valid -assumption for now. +to the BS operator from running a Tor client in any country that Tor +is still legal as it's not exit node, and the overhead in negligible. +The onion server is a 127.0.0.1 service, so cannot be seen by your ISP. +The BS service is on the opennet anyway so an onion is just another +access method. So we get dozens of Tor onion nodes running quickly, +we could test out running Tox *in* Tor using Hidden Services. If the +Tox nodebase was improved to serve BS nodes, it would be much more +resilient. I'm assuming the adversaries cannot block .onion addresses +within Tor, which I think is a valid assumption for now. There are [simple instructions](https://community.torproject.org/onion-services/setup/) to get Tor up and running, and you can test it by setting you browser @@ -24,7 +24,7 @@ to use the SOCKS proxy on ```127.0.0.1:9050```. Configure your boostrap server with an extra tcp_port that is not listed publically in the nodes.json file. We will use 33446 as an example. -In your ```/etc/tor/torrc`` or equivalent, you need to add 2 sections. +In your ```/etc/tor/torrc``` or equivalent, you need to add 2 sections. The first is: ``` @@ -44,9 +44,9 @@ Replace 33446 with your real port number. The next time tor starts up, a new directory will be created in ```/var/lib/tor/tox-hsv3/``` and it will have a file called ```hostname```. Look in the file for the onion address to your site. -Now add the onion address followed by a colon and post it to the -[mailinglist](https://lists.tox.chat/pipermail/bootstrap/), -along with your node's public key. +Now add the onion address followed by a colon and the port number +and post it along with your node's public key to the +[mailinglist](https://lists.tox.chat/pipermail/bootstrap/). You can also add this pair to the onions slot in your entry in the DHTnodes.json file. If there is not an onions slot, create one. @@ -55,3 +55,4 @@ DHTnodes.json file. If there is not an onions slot, create one. Details: * https://git.plastiras.org/emdee/tox_profile/ToxAndTorInChinaAndIran * https://community.torproject.org/onion-services/setup/ +* https://community.torproject.org/onion-services/