Hacker News Reader

Comment by ur-whale | Hacker News Reader

The real question is the kind of liability you take on when running a tor node on a machine that "belongs" to you (for some definition of belong).

Another is to find a place that will agree to power your machine and allow it to hook in to the ethernet if it runs a tor node.

At any rate, running a tor node isn't as simple as running apt-get.

View on HN

Running an entry or exit node is kinda risky since your IP will be associated with a lot of illegal content. Running an intermediary node is much safer. All kinds of nodes are important for the network.

The amount of configuration you need to run a node isn't terribly difficult. There is plenty of documentation online and really it's just changing a few lines in the config file. The Tor daemon is pretty good about pointing out potentially undesirable configuration options if you watch the log file on startup.

Just exit nodes are dangerous. FYI All relays are entry nodes.

I run two relay nodes. It is exactly as simple as running apt-get and editing the config.

BBC fights censorship in China, you would do the same by running a tor node.

When the secret police show up at your door, be sure to tell them that. I'm sure they will leave you alone.

I wonder what other places the BBC is blocked in. I know there's a DNS block in Viet Nam.

Is it possible to operate a TOR node through a corporate entity? The corporation assumes liability as does insurance.

That's not how liability works. People within the business will be on the line if the business is acting criminally.

You aren’t liable as a tor exit operator. That doesn’t mean you won’t get involved in nonsense or won’t be forced to get a lawyer to prove that but in the end you aren’t liable.

Reply on news.ycombinator.com