[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Putty usage in docs

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Sat, 10 Jan 2009 21:53:44 +0000

2009/1/9 Josh Bialkowski <josh.bialkowski_at_gmail.com>:
> To the documentation maintainer,
>
> I have a suggestion for the documentation in Appendix G, "Test using
> PuTTY" (G.5). In the docs it says
>
>> Click on Open and you should see a telnet style login
>> prompt. Use svnuser as the user name and if all is
>> well you should connect directly without being
>> prompted for a password.
>
> However, in the setup section, we setup a key with a passphrase so in
> fact PuTTY will say something like:
>
>> login as: ######
>> Authenticating with public key "imported-openssh-key"
>> Passphrase for key "imported-openssh-key":
>
> where imported-openssh-key is the default text in the "comment" field
> in the puttygen conversion tool. True this is not a _password_ prompt
> from the server, but it still confused me a little as I'm not all
> _that_ familiar with ssh and security and all that. From reading, it
> seems this is needed by PuTTY to decode the private key before sending
> it to the server (details are fuzzy for me). Anyhow you can avoid
> having to type that in by running Pageant, which is the putty agent
> (task-bar docked program that will store passphrases for decoding
> private keys). In this case you actually will connect without being
> prompted for a password and then the user can connect without typing
> in any passwords.

What do you suggest as an alternative text? Sorry, I have never used
PuTTY myself - this is text contributed by others.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
Received on 2009-01-10 22:54:26 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.