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

Re: still can't get svn+ssh to work with javasvn and private key

From: Dan North <dan_at_tastapod.com>
Date: 2005-09-27 09:42:03 CEST

Hi Alex.

I worked out last night what the problem is.

Your reply pointed me in the right direction. I don't know what the
exact cause is, but I've managed to reproduce the symptoms using the
command line client outside of Eclipse.

I use a url of the form: svn+ssh://someone_else@host.com/repos

When I update using this url, the command line works fine, and uses the
private key as I would expect.

However, when I use the url like this:

    svn ls --username someone_else svn+ssh://host.com/repos

it fails because it tries to use my local username "dan" instead of
"user". It seems that the svn+ssh protocol ignores the --username
parameter (at least for codehaus.org), so I /have/ to pass through the
full user@host.com url. Otherwise the remote sshd tries to match the key
against user "dan" (which doesn't exist at codehaus.org).

It turns out that codehaus also supports https access with regular
username and password, so I have switched to using that. However I think
it will be useful for javasvn to understand user@host urls and pass them
through correctly for other repositories that only support svn+ssh.

Thanks for all your help,
Dan

Alexander Kitaev wrote:

>Hello,
>
>I'm now using svn+ssh only myself just to test it more. So far it works fine
>for me. I'm using private key without password.
>
>
>
>>Firstly it isn't recognising the username from the subversion
>>url (someone_else@remote.site), so I'm setting it in the
>>dialog. I then give it the path to the key file and the
>>passphrase, and it still isn't working. Just keeps
>>redisplaying the dialog box.
>>
>>
>JavaSVN doesn't recognize username in the URL, so you should remove it from
>the URL and type into the dialog.
>
>When dialog is redisplayed, that means that JavaSVN was not able to
>authenticate you using provided information. Please make sure that:
>
>1. key file exists and it is valid OpenSSH (not Putty's PPK) private key.
>2. key is not encrypted with passphrase and if it is, specify this
>passphrase in the dialog.
>3. check server's logs if possible - it could reveal the reason of the
>problem.
>
>Alexander Kitaev,
>TMate Software,
>http://tmatesoft.com/
>http://tmate.org/
>
>
>
>>-----Original Message-----
>>From: Dan North [mailto:dan@tastapod.com]
>>Sent: Friday, September 23, 2005 20:10
>>To: users@subclipse.tigris.org
>>Subject: still can't get svn+ssh to work with javasvn and private key
>>
>>Hi folks.
>>
>>Mark: thanks for the updated plugin - I'm now getting the
>>dialog asking for my private key and passphrase.
>>Unfortunately, it's not working for me.
>>
>>Firstly it isn't recognising the username from the subversion
>>url (someone_else@remote.site), so I'm setting it in the
>>dialog. I then give it the path to the key file and the
>>passphrase, and it still isn't working. Just keeps
>>redisplaying the dialog box.
>>
>>The repository I'm looking at (jbehave.codehaus.org) only
>>supports key-based authentication, so I'm stumped.
>>
>>As always, any help gratefully received.
>>
>>ps. I just discovered that the command line adapter actually
>>updates - woohoo! - but I seem to recall being told it was
>>either unstable or not to be trusted with small children or
>>something..?
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>>For additional commands, e-mail: users-help@subclipse.tigris.org
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
Received on Tue Sep 27 17:42:03 2005

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

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