Currently these options are supported: --tor {disable,enable,always}.
--tor always is designed to run alongside the Tor process, and means that ZeroNet will use the Tor controller port to create the hidden service and Tor's SOCKS5 port to connect to the peers.
However, people sometimes also run Tor-connected VMs. This is actually the most secure way to connect to the Tor network, see for example the Whonix and Qubes projects. The suggested --tor inside option will work the same way as --tor always works with these exceptions:
- NetZero will not use SOCKS5, instead it will just connect to all peers directly, and perform DNS queries directly too, dark and clear nets alike.
- NetZero will not use the Tor controller port, instead the HS address and port will be supplied as an additional, required argument, for example
--tor_hidden_service {hs1}.onion:{port1}{:{hs2}.onion:{port2}{:...}}. User will create hidden service(s) and route it/them to that port(s).
Currently these options are supported:
--tor {disable,enable,always}.--tor alwaysis designed to run alongside the Tor process, and means that ZeroNet will use the Tor controller port to create the hidden service and Tor's SOCKS5 port to connect to the peers.However, people sometimes also run Tor-connected VMs. This is actually the most secure way to connect to the Tor network, see for example the Whonix and Qubes projects. The suggested
--tor insideoption will work the same way as--tor alwaysworks with these exceptions:--tor_hidden_service {hs1}.onion:{port1}{:{hs2}.onion:{port2}{:...}}. User will create hidden service(s) and route it/them to that port(s).