I'm not sure why this is or was a concern.

If you're telling Tortoise to use the system OpenSSH two things are 
probably happening:

1. There was an option so you clicked it,
2. You're using the system OpenSSH to manage your ssh and do things like 
add keys, edit the config, by hand or with Visual Studio Code or something, 
and you want TortoiseSVN to consume not manage,

A suitable warning should suffice to discourage (1), and in the case of (2) 
what happens now is far more unacceptable. After 2 decades of using Putty I 
_haven't_ used it in 5 years now and it took me a while to even remember 
why I was being asked for a "plink password" - just for a moment I actually 
thought "malware!"

In the subversion config file, there's the whole thing of adding "-q" to 
the SSH command and ssh knowing to suggest you turn it off so you can see 
why something that expected input failed.

So add a simple toggle between "Use Tortoise's Plink for SSH" and "Use 
System OpenSSH" with a big, bold disclaimer that user is responsible for 
authentication working in this scenario. An "Edit" for the user's 
~/.ssh/config would be gravy.

Plink -> Guided, hand-held authentication like you'd expect
OpenSSH -> The gates of hell are open, your spikey welcome wagon awaits

That said, currently (TortoiseSVN 1.14.3, Build 29387 - 64 Bit , 2022/04/08 
19:31:22) OpenSSH works fine right for trivial use but then you reach 
something like Merge -> Show Log and you have TortoisePlink asking for a 
password, because I'm not running (or going to) run pageant, and 
tortoiseplink feels like a bad windows citizen(*) that doesn't respect the 
user's now-builtin .ssh profile/configuration/keys/etc.

(* But, of course, that's because I'm actively using the built-in openssh 
rather than the putty ecosystem)



- Oliver

On Thursday, March 29, 2018 at 12:48:58 AM UTC-7 Stefan wrote:

> Sorry, there's no way.
> That's why we have to ship TortoisePlink and not just plink: TortoisePlink 
> is a modified version of plink that has many changes done so that the cmd 
> window does not appear.
> So as long as you can not change the code of the windows ssh client, 
> you're out of luck.
>
> Stefan
>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/2d90e941-42a3-416f-babc-212f709b6d22n%40googlegroups.com.
  • TortoiseS... tortoisesvn+APn2wQfnw2fAUX2MzIo65jZeA1rH_G1LHeH3ZvHbpFrj9UVz1cjw
    • Re: ... Stefan via TortoiseSVN
      • ... Paul Klapperich via TortoiseSVN
      • ... tortoisesvn+APn2wQeOV-P8kMQ5PVKZAWqQNFTv5RNqTmU96DRHeL6dZAWTDBjp
        • ... Stefan via TortoiseSVN
          • ... tortoisesvn+APn2wQfV2gM2BYWPzNZvnd4gLtGAH3pf6rgXAIOBrObRHbNf5ZsR
            • ... TortoiseSVN
              • ... Stefan via TortoiseSVN
              • ... tortoisesvn+APn2wQfV2gM2BYWPzNZvnd4gLtGAH3pf6rgXAIOBrObRHbNf5ZsR
      • ... Oliver Smith via TortoiseSVN
    • Re: ... tortoisesvn+APn2wQdgxbK3CgqO2rgIXa1GkHQUmRhnDw3JvLUkhfgFyEU8pV-6

Reply via email to