Hello, I wonder what is the reason not to offer the socks port publicly to users as an entrance point to the tor network?
Assume you run a tor exit or relay on a public server and you enable the socks port and listen on 0.0.0.0 or so and accept all incomming connections. Then you post the socks port publicly. What are the reasons not to do so?
Thanks yl
Hello yl,
you can do it if you want. But the traffic between you and the server is unencrypted. I think that's the main reason.
~Josef
Am 24.03.2015 um 23:09 schrieb yl:
Hello, I wonder what is the reason not to offer the socks port publicly to users as an entrance point to the tor network?
Assume you run a tor exit or relay on a public server and you enable the socks port and listen on 0.0.0.0 or so and accept all incomming connections. Then you post the socks port publicly. What are the reasons not to do so?
Thanks yl _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Am 24.03.2015 um 23:16 schrieb Josef Stautner:
you can do it if you want. But the traffic between you and the server is unencrypted. I think that's the main reason.
Thanks for the answer, it is obvious, just didn't consider that part of the connection. Thanks also to Moritz.
yl
On 03/24/2015 11:09 PM, yl wrote:
Assume you run a tor exit or relay on a public server and you enable the socks port and listen on 0.0.0.0 or so and accept all incomming connections. Then you post the socks port publicly. What are the reasons not to do so?
SOCKS does not encrypt traffic at all; all your traffic will travel to the SOCKS server in plain. Also, you need to fully trust the provider of the SOCKS port -- Tor is designed so you don't have to trust any participant in the network.
tor-relays@lists.torproject.org