On Fri, Oct 18, 2024 at 01:58:21PM +0200, Nils Rennebarth wrote: > Hi, > > On 18.10.24 13:50, Chris Green wrote: > > chris$ ps -fe | grep ssh-agent > > chris 2463 1530 0 12:33 ? 00:00:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh > > > > > but:- > > > > chris$ env | grep SSH > > SSH_AUTH_SOCK=/run/user/1000/keyring/ssh > > > > So SSH_AUTH_SOCK doesn't appear to be the socket that ssh-agent thinks > > it should be. > > > > This is on a fairly standard/default xubuntu 24.04 installation, I've > > not played about with the agent stuff (or at least I don't think I > > have). > > Can anyone suggest what might be awry? > You are probably running gnome-keyring which acts as a replacement ssh > agent and has slightly different behaviour: It will still list your keys > after > -D, but you need to unlock each them to actually use th > Ah, yes, of course. I looked at seahorse which configures that but forgot about gnome-keyring-daemon itself. There shouldn't be an ssh-agent as well as gnome keyring I assume, I'll have to try and work out what's starting what. Thank you. -- Chris Green _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
