The Stack Overflow podcast is back! Listen to an interview with our new CEO.
2 replaced http://tor.stackexchange.com/ with https://tor.stackexchange.com/
source | link

The details of how exactly hidden services workhow exactly hidden services work are a bit complicated, but the important part for this question is that both the client and the server build their own 3-node circuit to a meeting point in the middle. Thus, even if you altered your client code to connect to a known compromised exit node, the only thing that node knows is the "exit node" of the server's connection. Under the same principles that normally protect websites from reversing the circuit to know who you are, you similarly cannot reverse that circuit to know who the hidden service is.

The most dangerous node for a hidden service is its guard node, which is why the tor project made it harder to become one after the CMU attack was made public.

The details of how exactly hidden services work are a bit complicated, but the important part for this question is that both the client and the server build their own 3-node circuit to a meeting point in the middle. Thus, even if you altered your client code to connect to a known compromised exit node, the only thing that node knows is the "exit node" of the server's connection. Under the same principles that normally protect websites from reversing the circuit to know who you are, you similarly cannot reverse that circuit to know who the hidden service is.

The most dangerous node for a hidden service is its guard node, which is why the tor project made it harder to become one after the CMU attack was made public.

The details of how exactly hidden services work are a bit complicated, but the important part for this question is that both the client and the server build their own 3-node circuit to a meeting point in the middle. Thus, even if you altered your client code to connect to a known compromised exit node, the only thing that node knows is the "exit node" of the server's connection. Under the same principles that normally protect websites from reversing the circuit to know who you are, you similarly cannot reverse that circuit to know who the hidden service is.

The most dangerous node for a hidden service is its guard node, which is why the tor project made it harder to become one after the CMU attack was made public.

1
source | link

The details of how exactly hidden services work are a bit complicated, but the important part for this question is that both the client and the server build their own 3-node circuit to a meeting point in the middle. Thus, even if you altered your client code to connect to a known compromised exit node, the only thing that node knows is the "exit node" of the server's connection. Under the same principles that normally protect websites from reversing the circuit to know who you are, you similarly cannot reverse that circuit to know who the hidden service is.

The most dangerous node for a hidden service is its guard node, which is why the tor project made it harder to become one after the CMU attack was made public.