Tunnel Manager key management improvements #339

New Issue

idk · 2025-04-21T15:07:35-04:00

idk commented

2025-04-21 15:07:35 -04:00

Opened 3 months ago

Last modified 3 months ago

#2799 new enhancement

Tunnel Manager key management improvements

Reported by:ReportageOwned by:
Priority:
minor
Milestone:
undecided
Component:
apps/i2ptunnel
Version:
0.9.48
Keywords:
i2ptunnel, key management
Cc:

Parent Tickets:

Sensitive:
no

Description

To improve the overall user experience for managing private key files in the tunnel manager, the following changes are proposed:

Display the full path to the private key file in the UI, not just the key name (the alternate private key field for DSA hosts already does this)
Create new keys in a sub-directory of $config_dir e.g. .i2p/private_keys/ for easier management/backup
Create a sub-dir within .i2p/private_keys/ for inactive/deleted tunnel keys
Force the user to provide a name for new keys for easier subsequent identification
Implement a separate page to manage all private keys with an option to import/export keys via the file manager

Subtickets

Opened [3 months ago](/timeline?from=2021-01-24T16%3A11%3A04Z&precision=second "See timeline at Jan 24, 2021 4:11:04 PM") Last modified [3 months ago](/timeline?from=2021-01-29T03%3A10%3A01Z&precision=second "See timeline at Jan 29, 2021 3:10:01 AM") ## [\#2799](/ticket/2799)[new](/query?status=new)[enhancement](/query?status=!closed&type=enhancement) # Tunnel Manager key management improvements Reported by:[Reportage](/query?status=!closed&reporter=Reportage)Owned by: Priority: [minor](/query?status=!closed&priority=minor) Milestone: [undecided](/milestone/undecided "No date set") Component: [apps/i2ptunnel](/query?status=!closed&component=apps%2Fi2ptunnel) Version: [0.9.48](/query?status=!closed&version=0.9.48) Keywords: [i2ptunnel](/query?status=!closed&keywords=~i2ptunnel), [key](/query?status=!closed&keywords=~key) [management](/query?status=!closed&keywords=~management) Cc: Parent Tickets: Sensitive: [no](/query?status=!closed&sensitive=0) ### Description To improve the overall user experience for managing private key files in the tunnel manager, the following changes are proposed: - Display the full path to the private key file in the UI, not just the key name (the alternate private key field for DSA hosts already does this) - Create new keys in a sub-directory of $config\_dir e.g. .i2p/private\_keys/ for easier management/backup - Create a sub-dir within .i2p/private\_keys/ for inactive/deleted tunnel keys - Force the user to provide a name for new keys for easier subsequent identification - Implement a separate page to manage all private keys with an option to import/export keys via the file manager ### Subtickets

idk added this to the undecided milestone 2025-04-21 15:07:35 -04:00

idk added the #2799 apps i2ptunnel undecided labels 2025-04-21 15:07:35 -04:00

idk commented

2025-04-21 15:07:36 -04:00

comment:2 Changed 3 months ago by Reportage

Regarding the location of key storage, storing them in the root of the config dir with a separate i2ptunnel-keyBackup dir is messy. Given that most applications have a containing folder there, perhaps 'i2ptunnel' could be a good place to store the keys, with the backups in a sub-folder named 'backup' or somesuch.

In the root dir there's also keystore and keyBackup, which is obviously why i2ptunnel-keyBackup was chosen as the name of the backup dir.. less than optimal.

Forcing the user to name the key at the point the tunnel is created would avoid the awful naming scheme currently in play for keys.

And for consistency and discoverability, the full path to the generated key should be displayed in the UI.

Legacy isn't a reasonable justification for not addressing what are fundamental UX issues.

[comment:2](https://trac.i2p2.de/\#comment:2) Changed [3 months ago](https://trac.i2p2.de//timeline?from=2021-01-29T03%3A10%3A01Z&precision=second "See timeline at Jan 29, 2021 3:10:01 AM") by Reportage Regarding the location of key storage, storing them in the root of the config dir with a separate i2ptunnel-keyBackup dir is messy. Given that most applications have a containing folder there, perhaps 'i2ptunnel' could be a good place to store the keys, with the backups in a sub-folder named 'backup' or somesuch. In the root dir there's also keystore and keyBackup, which is obviously why i2ptunnel-keyBackup was chosen as the name of the backup dir.. less than optimal. Forcing the user to name the key at the point the tunnel is created would avoid the awful naming scheme currently in play for keys. And for consistency and discoverability, the full path to the generated key should be displayed in the UI. Legacy isn't a reasonable justification for not addressing what are fundamental UX issues.

idk commented

2025-04-21 15:07:36 -04:00

comment:1 Changed 3 months ago by zzz

a lot of this is just legacy from the way i2ptunnel has always stored tunnels.

we already have a i2ptunnel-keyBackup directory.

related: #752 #2121

[comment:1](https://trac.i2p2.de/\#comment:1) Changed [3 months ago](https://trac.i2p2.de//timeline?from=2021-01-28T18%3A34%3A42Z&precision=second "See timeline at Jan 28, 2021 6:34:42 PM") by zzz a lot of this is just legacy from the way i2ptunnel has always stored tunnels. we already have a i2ptunnel-keyBackup directory. related: [#752](https://trac.i2p2.de//ticket/752 "#752: enhancement: backup keyfiles (open)") [#2121](https://trac.i2p2.de//ticket/2121 "#2121: enhancement: Improve import/export of tunnel keys in tunnel manager (open)")

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: I2P_Developers/i2p.i2p#339

Tunnel Manager key management improvements #339

#2799newenhancement

Tunnel Manager key management improvements

Description

Subtickets

#2799 new enhancement