I am getting the password dialog over and over again
TortoiseSVN (or better its SSH client TortoisePlink) can't find a key for the current user. Run pageant and add your private key or define a putty session with a private key included.
Try saving another copy of the key after clearing the passphrase and use that new key. Putty no longer prompts for a passphrase.
google search
|
|
|
Comments
The real solution is simple
I beat my head against the wall for an hour going around in circle only to find a post at svnforums.org the fixes the problem. Change your ssh client in Tortoisensvn from putty.exe to C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe .
this worked for me... thanks
this worked for me... thanks a lot!
Might need to add -l username
In addition to the suggestions in the parent post, I needed to use "-l username" to make this work.
Otherwise the password prompt would just not accept my password. So the ssh client string becomes
C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe -l fill_your_user_name
no need to fill the ssh client setting
I had this problem too and what worked for me, was to leave the TortoiseSVN's ssh client-setting empty and use url:
svn+ssh://username@url/dirs
and thus no need to use "-l username" in settings
Yes, automatic
Yes, automatic authentication using pagent.exe will make the issue moot. But the root cause of the problem is that TortoiseSVN invokes its ssh client multiple times for some operations, instead of using one connection that is kept open.
Initial checkout is one such operation that causes 3 separate invocations of the ssh client, and thus 3 separate prompts for the password.
Also, please do not recommend that users keep an unencrypted private key on their system for login convenience! Users may not realize what a security hole this is. They should either use pagent or put up with the hassle.
Unencrypted Keys
Those who used WinXP Pro can at least encrypt the folder the keys are in. Right click on the folder or just the file and select properties -> Advanced -> Check encrypt contents and start clicking ok.
Of course it would be nice if it just used ssh once per operation.
Unencrypted Keys
Windows filesystem encryption will not protect against malware / spyware running under the users account (e.g. after compromising the users browser or mail client), only against other users accounts on the same machine and "external" access e.g. after a theft.