git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: egit and RSA keys for SSH

From
AHAaron Hicks <hicksa@landcareresearch.co.nz>
Date
Jun 15, 2009, 22:49 UTC
Message-ID
<F2969C1B08CBEE42B78C04C280D578E72CAF41E46A@donkey.landcare.ad.landcareresearch.co.nz>
In-Reply-To
<20090615150341.GX16497@spearce.org>
Hi Shawn,
I've followed your instructions, and added the same RSA key that I use with Git and Git Extensions (using Windows here), but eGit still asks for a password for a the git user (which is password disabled, and requires RSA). I'm telling eGit to access via "git + SSH".
I'm assuming for windows the ~/.ssh should be in C:\path\to\profile\username\.ssh ?
I'm not 100% that eGit has installed correctly in Eclipse (3.4.2 Ganymede, Windows XP SP3, Java 1.6.0_13) either. I can't see many git-like commands in the context menus for files and projects.
Regards,
Aaron Hicks
Show 52 quoted lines
> -----Original Message-----
> From: spearce@spearce.org [mailto:spearce@spearce.org]
> Sent: Tuesday, 16 June 2009 3:04 a.m.
> To: Aaron Hicks
> Cc: git@vger.kernel.org
> Subject: Re: egit and RSA keys for SSH
>
> Aaron Hicks <HicksA@landcareresearch.co.nz> wrote:
> > We have a git repository set up with gitosis and it requires RSA
> > keys to authenticate developers who have rights to push to this
> > repository. i.e. they are blessed with write privileges. Github
> > uses a similar method.
> >
> > We use Eclipse, so we would like Eclipse to integrate with Git. So
> > we grabbed egit from http://www.jgit.org/update-site and used the
> > Eclipse installer (Like we do all the other Eclipse plug-in, given
> > that the egit/jgit sites don't give instructions otherwise it seems
> > to be the thing to do).
> >
> > The problem is I can't see how to associate an RSA key in order
> > to authenticate the SSH login with our gitosis repository (or
> > GitHub). We have PuTTY installed and use Pageant to manage keys, and
> > the required key is already loaded.
>
> Unfortunately both PuTTY's Pageant and OpenSSH's ssh-agent are
> not supported from JSch, which is the SSH client used within JGit,
> which is what is underneath EGit.  Consequently, you can't use the
> agent to manage your keys.
>
> From within Eclipse, if you go to Window > Preferences > General >
> Network Connections > SSH2 you can configure your RSA keys.  But,
> these keys are configured globally for the workspace, i.e. its
> more like loading the key into the agent than it is about binding
> a particular key to a particular host.
>
> To force binding a key to a host, use ~/.ssh/config.  JGit knows
> how to read this file on startup and uses the Host blocks to do
> some configuration control over the connection.
>
> E.g. if you use a URL like "git@gitserver.example.com:foo.git"
> then you can put the following in your ~/.ssh/config to force using
> a specific SSH key:
>
>   Host gitserver.example.com
>     IdentityFile .ssh/id_gitkey
>
> Note that ~/.ssh/config is cached on startup of EGit, so you'll
> need to completely restart the Eclipse workspace after making any
> changes to it.
>
> --
> Shawn.
Please consider the environment before printing this email
Warning:  This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 5 of 6 in “egit and RSA keys for SSH”
  1. Aaron HicksJun 15, 2009
  2. Tay Ray ChuanJun 15, 2009
  3. Shawn O. PearceJun 15, 2009
  4. Shawn O. PearceJun 15, 2009
  5. Aaron HicksJun 15, 2009
  6. Shawn O. PearceJun 16, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.