13 Feb
2014
13 Feb
'14
2:32 a.m.
On 02/12/2014 01:20 AM, grarpamp wrote:
Note that Phantom allows both the service and the client to choose the number of hops under their respective control. I believe this applies in part to I2P as well. There is thus no force to accept any globally enforced maximum hopcount there. This concept may or not work for Tor.
This works in Tor as well. I don't remember seeing a strict hop count in the spec. A custom Tor client can choose any number of hops it wants.
In fact, the official Tor already has similar feature built in: Tor2Web mode, in which client does a direct connect to RP.