Opened 5 years ago
Closed 5 years ago
#1707 closed defect (fixed)
BOB defaults to 1-hop tunnels
Reported by: | dg | Owned by: | sponge |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.24 |
Component: | apps/BOB | Version: | 0.9.22 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description
BOB will create bob.config with a default of a 1-hop in/out tunnel.
#i2p-dev:
<ThePrudentNinja> Correction, another possible issue is with bob.config. It defaults to one hop tunnels with no randomization. Is that a problem or should that be addressed? <ThePrudentNinja> However the one hop tunnels look suspicious to me lol <+dg> It's not suspicious as such, it's a poor default though <ThePrudentNinja> I would think it would default to three hops
Should probably be bumped to three.
A limitation of BOB is that hops cannot be set by the user.
Subtickets
Change History (1)
comment:1 Changed 5 years ago by
Milestone: | undecided → 0.9.24 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Changed to 3 in 001f6936ef9ce64b8f28a8f6c81444533f89870b branch i2p.i2p.zzz.test2 to be propped for 0.9.24
Pretty sure that OP is incorrect, options may be set with the 'option' command, which is listed on http://i2p-projekt.i2p/en/docs/api/bob but is otherwise undocumented. In the code, it looks like it's "option key1=value1 key2=value2…" I'll add it to the spec.