Zeronet: [Doc] Tor Only (no IP leak) | Tor from the Start

Created on 15 Aug 2019  路  7Comments  路  Source: HelloZeroNet/ZeroNet

Documentation/Question: How do I configure ZeroNet not to send any requests not through TOR?

I know when in the console you can select TOR only, but for high risk users wouldn't their IP already be leaked? Is it not possible to set it to not use clear-net whatsoever?

Note: This issue is more related to high-risk users, as most people could just use a VPN.
But, nonetheless anybody may be concerned about IP anonymity.

Most helpful comment

All 7 comments

In zeronet.conf, add:

trackers_proxy = tor
tor = always

If you can get Tor Always to work.

@github-zeronet Could you please mention you are not the ZeroNet creator/maintainer in your profile bio? "github-zeronet" could be easily cofused with "HelloZeroNet".

Thanks.

In zeronet.conf, add:

trackers_proxy = tor
tor = always

If you can get Tor Always to work.

It seems that "tracker_proxy = tor" is wrong
https://github.com/HelloZeroNet/ZeroNet/issues/2158#issuecomment-522536944

Probably we should ignore the traker_proxy setting in tor=always mode

Probably we should ignore the traker_proxy setting in tor=always mode

I'm looking forward to understanding how Tor is used under the hood, but can only do so much in a day.

In the meantime, I've locked ZN down in a VM that has no way out except through Tor, and in this configuration, it is using Tor Always with trackers_proxy disabled. This configuration has been running for days, but I don't know if trackers can see the real IP if it wasn't inside this VM. If I'm using Tor Always without OS-level protection, how most run it, I'd expect no tracker or peers can see the real IP.

I just switched to trackers_proxy tor inside this VM. It worked w/o restart. Then restarted to clear any cache. Hours later, continues to work... no fade.

Is self.ip_type always "onion" when Tor always is enabled? If not, then this code change seems to disable Tor for trackers if Tor Always is selected, which is the opposite of what users expect and the behavior described in this comment.

Or is it that

self.createSocket()

uses Tor in Tor Always mode, and

self.sock = self.server.tor_manager.createSocket(self.ip, self.port)

isn't needed?

Note that I have the same issue as @HostFat outside the VM, including the fade where it sometimes initially works, and have yet to resolve this. But, since this works without issue inside this VM, I have to wonder if the problem isn't external configuration, such as firewall rules, or how Tor is configured.

In tor always mode we replace the socket object with a proxied one: https://github.com/HelloZeroNet/ZeroNet/blob/py3/src/util/SocksProxy.py#L21
https://github.com/HelloZeroNet/ZeroNet/blob/py3/src/main.py#L94

In this way every created socket object should be proxied without modifying the code.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yurivict picture yurivict  路  4Comments

jerry-wolf picture jerry-wolf  路  4Comments

yurkobb picture yurkobb  路  3Comments

ghost picture ghost  路  4Comments

trenta3 picture trenta3  路  3Comments