> I've been using TortoiseSVN for a long time now, and recently updated
> to "TortoiseSVN 1.5.6, Build 14908".
> When I try to connect to my friend's svn repository (svn+ssh), I can
> authenticate just fine. However, it gives me no option to save
> authentication. I actually get two prompts; one for username, then
> another for password. If I connect to a plain old svn repository, it
> says "<servername> Requests a username and password", and gives me a
> checkbox to save authentication. I know I USED to be able to save
> authentication for his server, because we worked on a project together
> in the past. Am I doing something wrong, or what?
For ssh authentication, you're *never* asked to save the password, not
now and not in any version before.
That's because the whole network traffic is tunneled over ssh, which
means Subversion (and TSVN) never even see the authentication challenge.
> As a side note, it really bothers me that the svn+ssh prompts take
> "Cancel" to mean "use blank". If you press cancel at the username
> prompt, you are now STUCK. It will repeatedly prompt for a password
> and try to connect with a blank username no matter how many times I
> try to cancel at the password prompt. My friend's server doesn't have
> a password lockout, so it just keeps asking and asking. I don't think
> being locked out of the server would be good either. All I can do is
> close the TortoiseProc and TortoisePlink with the task manager.
That's how Plink is implemented. And actually, Cancel sends an empty
string back to indicate the cancel. If the server doesn't react to that
(or reacts wrong) there's nothing Plink can do - and TortoisePlink is
just an UI patch to Plink.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-24 15:44:26 CET