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

Putty usage in docs

From: Josh Bialkowski <josh.bialkowski_at_gmail.com>
Date: Fri, 9 Jan 2009 08:46:34 -0800 (PST)

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.

I know that these docs are in no way designed to educate users on
PuTTY per se, but I still think it would be a useful and worthy
addition.

Thanks, and I hope you find this suggestion useful!

Josh Bialkowski

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1014029

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-09 17:48:58 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.