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

Re: After 1.5.0 upgrade, keeps prompting for ssh username

From: Ed Avis <eda_at_waniasset.com>
Date: Thu, 3 Jul 2008 16:29:15 +0000 (UTC)

I have fixed this problem. It turned out that plink itself, run from the
command line, also prompted for a username.

I had changed the default settings in Putty to give hostname linux01. When I
deleted this and put the default settings back to the Putty factory default,
things started working again.

I conjecture that this is because plink searches through the Putty settings for
the first configuration that has the hostname you wanted. In this case there
were two such configurations: one I had set up with hostname linux01 and an
auto-login username, but also the default settings. It found the default
settings first. But the Putty default settings do not allow you to specify an
auto-login username (I think it gets wiped when you press 'Save').

Why this coincided with the TortoiseSVN 1.5.0 upgrade is unclear. It might be
that an older version of tortoiseplink behaved differently. Or it could be
entirely unrelated.

I think there may be a couple of bugs to be fixed in Putty upstream:

- When you try to save overwriting the Default Settings, it should not silently
blank out the auto-connect username or other settings. It should instead prompt
you to delete these yourself before allowing you to save.

- plink should scan all the Putty configurations to find those matching the
hostname given, rather than taking the first. If there is more than one match
it should give an error.

-- 
Ed Avis <eda_at_waniasset.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-03 18:35:57 CEST

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