On Friday, May 8, 2020 at 9:54:37 PM UTC+2, Michael Cole wrote:
>
> Hi Stefan,
>
> - Where are the keys stored?  I think it goes through TortoisePlink.exe - 
> can I set the key when making the tunnel so I don't have to mess with 
> PuTTY's settings?
>
>>
>> Plink stores the keys, that's another application. TortoisePlink is just 
>> the original Plink compiled and slightly modified so that ugly console 
>> window doesn't pop up every time.
>>
>
> When TortoisePlink starts the connection, it sends a public key from a 
> well-known place to start securing the connection.  I want it to send a key 
> saved from the SSH config section.  So it could either write to the 
> well-known location - or use the configured one first.
>
> From TortoisePlink's help dialog, something like:
>
> tortoiseplink [host] -i [keyfile location]
>
>
you can configure the ssh client that svn uses like that if you like.
e.g. in the TSVN settings dialog, network, ssh client: just put something 
like this in there:
tortoiseplink -i path\to\keyfile
 

>   
>
>>
>>> - Can TortoiseSVN (or it's programs) create keys or does it need an 
>>> external program?  ( (I see \ext\openssl in the repo checkout)
>>>
>>
>> No, TSVN can't create keys. Sorry.
>>  
>>
>
> Windows 7 and later already has ssh-keygen installed at: 
> C:\Windows\System32\OpenSSH\ssh-keygen.exe  so we could shell that command 
> to generate the keys like just like plink to make the connection.
>
> It looks like most of the heavy lifting has been done.  Would you be 
> interested in a patch for this?
>
>
No, but generating keys is not the job of an svn client. I don't like the 
idea of implementing things that are not part of the main job of TSVN.

Stefan

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN-dev" 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-dev/8eee384e-bd96-4d2c-9d6d-0d26e78e5ad3%40googlegroups.com.

Reply via email to