Bug#493874: ssh-add -c reports SSH_AGENT_FAILURE and doesn't ask for confirmation
reassign 493874 gnome-keyring
severity 493874 wishlist
thanks
On Wed, Aug 06, 2008 at 05:27:27PM +0100, Colin Watson wrote:
> On Wed, Aug 06, 2008 at 01:28:19AM -0300, Wouter Verhelst wrote:
> > On Wed, Aug 06, 2008 at 01:35:13AM +0100, Colin Watson wrote:
> > > Is it possible that you are not in fact using ssh-agent, but a different
> > > not-quite-compatible agent provided by something like seahorse? Have a
> > > look at what's behind $SSH_AUTH_SOCK.
> >
> > Yes, that does appear to be the case; $SSH_AUTH_SOCK seems to be served
> > by gnome-agent. I apparently also can't get rid of it without removing
> > gdm.
>
> There's no match for "gnome-agent" in dists/unstable/Contents-i386.gz.
> Would you mind figuring out the correct package and reassigning this
> bug?
Sorry; it was 'gnome-keyring', which runs 'gnome-keyring-daemon'. I got
confused by the fact that ssh calls it an 'agent'.
To the maintainer of gnome-keyring: ssh-add has a '-c' option, which
will cause ssh-add to request from ssh-agent that it requests
confirmation from the user every time an application tries to access the
key; this is a benefit security-wise. It would be nice if gnome-keyring
were to implement this.
--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22
Reply to: