Opened 15 months ago

Last modified 12 months ago

#2121 open enhancement

Improve import/export of tunnel keys in tunnel manager

Reported by: Reportage Owned by:
Priority: minor Milestone: undecided
Component: apps/i2ptunnel Version: 0.9.32
Keywords: tunnelmanager, simple key export, UX Cc:
Parent Tickets:

Description

Currently, exporting tunnel configurations from one router to another is more complex than it needs to be. A simple option to export to file (zip?) a tunnel definition including the associated private key and configuration, and the option specify the file for easy import to another router would improve UX and facilitate easier deployment and perhaps encourage more use of multi-homing.

Subtickets (add)

Change History (2)

comment:1 Changed 15 months ago by zzz

  • Status changed from new to open

Related to / dup of #752 #1274 #1502

comment:2 Changed 12 months ago by slumlord

I have suggested this before, not sure if I made a a ticket for it (Ah, it was a comment on #1274 - comment: http://trac.i2p2.i2p/ticket/1274#comment:4 ). This would greatly improve the ease with which multihoming for a hidden service can be set up. Currently, one has to manually copy the keys to each router's working directory and manually set up the hidden service from scratch. If there is going to be a private key contained in the exported file, it would be good to have the option to password-protect the file.

Note: See TracTickets for help on using tickets.