Last spam from me for today:
11:22:34$ lsof | grep /tmp/keyring-wiGtof/socket.ssh
gnome-key 23368jon 18u unix 0x8101261f8380 0t099223
/tmp/keyring-wiGtof/socket.ssh
11:22:39$ ps -eaf|grep gnome-key
jon 23368 1 0 11:18 ?00:00:00 /usr/bin/gnome-keyring-
On Wed, Apr 15, 2009 at 11:18:20AM +0100, Jon Dowland wrote:
> I've just removed seahorse, logged out, restarted gdm, logged back in again
> and the problem remains, so it probably isn't actually seahorse, but it most
> likely isn't ssh agent either.
I've just tried the inverse, installing seahors
On Tue, Apr 14, 2009 at 12:01:17PM +0100, Colin Watson wrote:
> Are you sure that OpenSSH's agent is in fact the one being used here? GNOME
> has recently taken to using "seahorse" which has some bugs.
>
> You can tell the difference by typing 'echo $SSH_AUTH_SOCK'. A genuine
> OpenSSH agent will
On Tue, Apr 14, 2009 at 10:00:34AM +0100, Jon Dowland wrote:
> Recently, the ssh-agent instance started by xsession (as
> part of a GNOME desktop login) cannot use my public key,
> nor a newly generated passwordless RSA key.
>
> After adding a new user, logging into a fresh desktop
> session (no e
Package: openssh-client
Version: 1:5.1p1-5
Severity: important
Recently, the ssh-agent instance started by xsession (as
part of a GNOME desktop login) cannot use my public key,
nor a newly generated passwordless RSA key.
After adding a new user, logging into a fresh desktop
session (no existing $
5 matches
Mail list logo
