> On Sun, Jan 4, 2009 at 2:22 PM, <tommydkat_at_gmail.com> wrote:
> > I have Eclipse 3.2.2 installed on Ubuntu 8.10 Linux (64-bit). I also have subclipse 1.4.7 installed along with:
> > Subversion client adapter 1.5.2
> > Subversion Native Library Adapter (JavaHL) 1.5.5
> > SVNKit Client Adapter 1.5.4
> > SNVKit Library 188.8.131.5297
> > I have my remote SVN repository configured in Eclipse and it's displayed in the SVN Repositories browser.
> > When I connect to my SVN repository, I get prompted for the login information. The repository URL is "svn+ssh://my.website.com", the username is correct "tom", and I choose "use private key for authentication" and I navigate to where my private key is in my home directory (e.g. /home/tom/.ssh/private_key_rsa). I have no passphrase for my private key, so I leave that field blank. My SSH server is listening on a port other than 22, so I specify that port and I click "Ok".
> > The dialog window with my login information disappears for a second and comes right back. Clearly, the login attempt failed. If I use a userid/password to login, I can login just fine.
> > At the command line, I can login using ssh just fine:
> > ssh -p 12345 tom_at_my.website.com
> > I don't get any messages after the subclipse login with private key fails so I have no idea what the problem could be.
> > How can I find out what the problem is so I can correct it?
> Since you are on Linux, you are most likely using the SVNKit client
> adapter. The preferences ought to tell you this. You can check this
> page for instructions on getting JavaHL working:
> SVNKit provides its own pure Java SSH client library. Perhaps it is
> having problems with your key? support_at_svnkit.com is very responsive
> and likely has some logging they can tell you how to configure.
> JavaHL uses the same SSH infrastructure as the command line client so
> if the command line works, then so should JavaHL. If you need to
> provide a passphrase to unlock your key, you should use ssh-agent so
> that this is managed for you. One of the negatives to using JavaHL
> with SSH is that there is no console window available to respond to
> any prompts provided by the OpenSSH client. So it is best to make
> sure you are setup to not need to respond to any such prompts.
Ok, I got it working!!!! It turns out to be a passphrase that was getting in the way. Previously, I had logged in via ssh and specified my passphrase and subsequent tries didn't require me to enter a passphrase. Once I removed the passphrase, it started working.
I feel like an idiot.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-01-09 19:26:33 CET