#1088 closed enhancement (fixed)
SOCKS type should support persistent keys
| Reported by: | dg | Owned by: | dg |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.9 |
| Component: | apps/i2ptunnel | Version: | 0.9.8.1 |
| Keywords: | easy | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
I2PTunnel's SOCKS tunnel type does not support persistent keys as a form of identification.
I use a SOCKS tunnel for convenience when SSHing among other things, the ability to restrict access without converting to a tunnel-per-host would be great!
Thanks.
Subtickets
Change History (6)
comment:1 Changed 6 years ago by
comment:2 Changed 6 years ago by
| Keywords: | easy added |
|---|---|
| Milestone: | 0.9.9 → 0.9.12 |
The I2PSOCKSTunnel constructor already supports a private key file argument (since it is extended by I2PSOCKSIRCTunnel which supports it).
So requires only simple changes in I2PTunnel.java and TunnelController?.java to pass the argument through, and editClient.jsp to unhide the settings.
Adding tag 'easy'.
related: #451
comment:4 Changed 6 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in 0.9.8.1-14 40e39576b76cc1261e0eda2c63a052544021f2e3
comment:5 Changed 6 years ago by
| Owner: | set to dg |
|---|
comment:6 Changed 6 years ago by
| Milestone: | 0.9.12 → 0.9.9 |
|---|
Setting milestone to 0.9.9 as per the dev guidelines. The fix will appear in this release.
Note: See
TracTickets for help on using
tickets.
I do not use encrypted leasesets as I am told the encryption is weak.