Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#936 closed defect (fixed)

Default new tunnel to 3 hops

Reported by: DISABLED Owned by:
Priority: minor Milestone: 0.9.7
Component: apps/i2ptunnel Version: 0.9.5
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

IMO, I2PTunnel should set Length(t) to 3 hop tunnels, not 2 by default.

Latency is variable (as we know) and 3 hop tunnels are immune to attacks that 2 are not. According to Tor[1], 3+ hop tunnels have the same levels of immunity to a variety of attacks a 3 hop tunnel. zzz has commented on this previously but with no conclusion[2].

I feel the avg. user will not notice a large difference and those who wish to gain speed may do so by modifying the default option.

[1] https://blog.torproject.org/blog/one-cell-enough
[2] http://zzz.i2p/topics/299

Subtickets

Change History (5)

comment:1 Changed 6 years ago by zzz

Component: unspecifiedapps/i2ptunnel
Milestone: 0.9.60.9.7

comment:2 Changed 6 years ago by zzz

Resolution: fixed
Status: newclosed

comment:3 Changed 6 years ago by zzz

Wizard fixed in 0.9.6-3

comment:4 Changed 6 years ago by DISABLED

How about 3 hop default for exploratory and I2PSnark? It seems it was planned for exploratory a while ago but never happened for ??? reasons.

It may have an effect on speed in I2PSnark but it shouldn't be for a concern in exploratory, imo.

comment:5 Changed 6 years ago by zzz

opened #966

Note: See TracTickets for help on using tickets.