Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

tortoiseplink feature requests

14 views
Skip to first unread message

Jon Marnock

unread,
Aug 8, 2024, 1:20:35 AM8/8/24
to TortoiseSVN
Hi,

Couple of feature requests:

1. $USERNAME support

In the tunnel section we can use $SVN_SSH to stand in for the SVN_SSH environment variable in windows, but this is not quite the same as just a slightly awkward way to refer to an environment variable, as it doesn't appear to allow any others (eg, $USERNAME or %USERNAME% both are not expanded to the USERNAME environment variable).

Not as big a deal, but it also expects the format of that SVN_SSH thing to have fully\\escaped\\backslashes, or use/forward/slashes instead for the path - feels quirky.

Is it possible to have tortoise understand at least some of the environment variables and allow them in that tunnel config section?

2. Better handling of multiple hardware certificates

Currently, I have two hardware certificates used to authenticate via pageant. One is stored securely at one location, the other at another offsite location.

Both are added to my pageant config, and whenever I'm at one location, it tries the certificates only available at the other first, windows pops up a prompt that says the certificate isn't available and gives me the option to insert the hardware token or click cancel.

In putty, I click cancel and it then moves onto the second certificate, which then prompts me for a pin to unlock it, and then it succeeds. In TortoiseSVN, if I click cancel on the first certificate, tortoiseplink seems to interpret that as a permanent hard fail and it just fails the operation immediately rather than allowing me to attempt the second certificate.

If I switch to using the native plink.exe file it works fine - I hit cancel on the missing cert, and it just asks for the pin on the second one, and then tortoise continues.

Can we have tortoiseplink properly parse the responses and only assume the thing has fully failed when it's reached the end of the authentication options, rather than just immediately dying when it hits the first softfail?

For reference, this is what it looks like in plink when in this situation:

Pageant is running. Requesting keys.
Pageant has 2 SSH-2 keys
Using username "<redacted>".
Trying Pageant key #0
Authenticating with public key "CAPI:9<redacted>e" from agent
Sending Pageant's response
Server refused public-key signature despite accepting key!
Trying Pageant key #1
Authenticating with public key "CAPI:9<redacted>b" from agent
Sending Pageant's response
Access granted
Opening main session channel

(after the first "CAPI" line, I hit cancel on the gui prompt, and on the second, I enter the pin)

Regards,
Jon.


Reply all
Reply to author
Forward
0 new messages