Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Operating as an exit node exposes you to a great deal of legal issues, if not liability.

Not to mention annoyance for the user... there will be sites you can't access since many sites block exit node IPs outright because of abuse.

If some random does something illegal and they happen to be using your node, guess who gets the knock on the door?

With that in mind, what user would want to operate an exit node?



What about hidden services? In my opinion that's the real heart of Tor. I think the value of exit nodes will start to wane as Tor gains a larger and larger user base and becomes it's own truly viable darknet. As it stands the majority of security related discussions I've come across regarding Tor strongly discourage spending any large amount of time on clearnet services anyway as this create many potential security/privacy risks.


If you are more interested in the hidden services aspect, did you also have a look at I2P [1]? It is more geared toward this aspect (exit nodes = outproxies in i2p-speak for example are just standard hidden services)

[1] https://geti2p.net/


Thanks! i2p is on my list of 'privacy stuff to learn' but your comment may have bumped it up a bit in priority.


"With that in mind, what user would want to operate an exit node?"

All of the people who have already been running exit nodes for years? Those who don't mind getting that terrible knock on the door? Those who have already had that knock on their door, sometimes more than once, but who live in locations where they don't need to fear their local police?


     what user would want to operate an exit node?
I'm thinking that malicious individuals would run Tor exit nodes in order to sniff traffic.


They can, and they do. Which is why you need to use encryption as well as Tor if you want to something private. But that's the case without Tor anyway.


In theory you could run an exit node with a locked down exit policy, e.g. limited to web traffic which is routed through an IWF compliant proxy, disallow HTTPS and/or payment processing sites, add an HTTP header for reporting abuse/requesting blocks, etc.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: