From e5e37850a534b7464058c043a3397e92788a0462 Mon Sep 17 00:00:00 2001 From: unsystemizer Date: Tue, 3 May 2016 12:04:17 +0800 Subject: [PATCH 1/3] Clarify ZeroNet with Tor on Linux --- docs/faq.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index aaa2127..2846666 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -75,7 +75,10 @@ Edit config to enable control protocol: - Add permission yourself to read the auth cookie by `usermod -a -G debian-tor [yourlinuxuser]`
(if you are not on Debian check the file's user group by `ls -al /var/run/tor/control.authcookie`) - Logout/Login with your user to apply group changes -> __Tip:__ You can verify if your Tor running correctly using `echo 'PROTOCOLINFO' | nc 127.0.0.1 9051` +Start Tor, and then start ZeroNet like this: `zeronet.py --tor always`. + + +> __Tip:__ You can verify if your Tor running correctly using `echo 'PROTOCOLINFO' | nc 127.0.0.1 9051`. If ZeroNet cannot access Tor, consider adding `CookieAuthFileGroupReadable 1` and `CookieAuthFile ` to your Tor configuration file. > __Tip:__ It's also possible to use without modifying torrc (or using older version of Tor clients) by running it `zeronet.py --tor disable --proxy 127.0.0.1:9050 --disable_udp`, but then you will loose ability to talk with other .onion addresses. @@ -198,7 +201,7 @@ ZeroNet is built for dynamic, real-time updated websites, but you can serve any #### How can I create a new ZeroNet site? -[Follow those instructions.](/using_zeronet/create_new_site/) +[Follow these instructions.](/using_zeronet/create_new_site/) --- From 42fb5f0ed8c60381520f918a7d3f349b9e2cb157 Mon Sep 17 00:00:00 2001 From: unsystemizer Date: Wed, 4 May 2016 16:38:38 +0800 Subject: [PATCH 2/3] Added "enable" --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 2846666..89dfd4b 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -75,7 +75,7 @@ Edit config to enable control protocol: - Add permission yourself to read the auth cookie by `usermod -a -G debian-tor [yourlinuxuser]`
(if you are not on Debian check the file's user group by `ls -al /var/run/tor/control.authcookie`) - Logout/Login with your user to apply group changes -Start Tor, and then start ZeroNet like this: `zeronet.py --tor always`. +Start Tor, and then start ZeroNet like this: `zeronet.py --tor always`. For concurrent dual (clearnet and Tor) use, use `--tor enable`. > __Tip:__ You can verify if your Tor running correctly using `echo 'PROTOCOLINFO' | nc 127.0.0.1 9051`. If ZeroNet cannot access Tor, consider adding `CookieAuthFileGroupReadable 1` and `CookieAuthFile ` to your Tor configuration file. From 43df3c10861d17a801547b69a3ab5b4c243ba38b Mon Sep 17 00:00:00 2001 From: unsystemizer Date: Wed, 4 May 2016 16:42:14 +0800 Subject: [PATCH 3/3] Clarify permissions --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 89dfd4b..a4bfa18 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -78,7 +78,7 @@ Edit config to enable control protocol: Start Tor, and then start ZeroNet like this: `zeronet.py --tor always`. For concurrent dual (clearnet and Tor) use, use `--tor enable`. -> __Tip:__ You can verify if your Tor running correctly using `echo 'PROTOCOLINFO' | nc 127.0.0.1 9051`. If ZeroNet cannot access Tor, consider adding `CookieAuthFileGroupReadable 1` and `CookieAuthFile ` to your Tor configuration file. +> __Tip:__ You can verify if your Tor running correctly using `echo 'PROTOCOLINFO' | nc 127.0.0.1 9051`. If ZeroNet user cannot access the Tor authentication cookie file, ensure you have `CookieAuthFileGroupReadable 1` and `CookieAuthFile /full/path/to/cookie/file>` that is accessible to user(s) who runs ZeroNet and Tor. > __Tip:__ It's also possible to use without modifying torrc (or using older version of Tor clients) by running it `zeronet.py --tor disable --proxy 127.0.0.1:9050 --disable_udp`, but then you will loose ability to talk with other .onion addresses.