Confusion using "ssh-add -D" and then "ssh-add -l"

[Nils Rennebarth]

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


-- 
Dipl. Math Nils Rennebarth
Senior Berater Entwicklung
Division Network & Client security
secunet Security Networks AG


Tel.: +49 201 5454-3976
Fax: +49 711 900300-90
Mobil: +49 174 9750449
E-Mail: nils.rennebarth at secunet.com


Neue Brücke 3
70173 Stuttgart
www.secunet.com

______________________________________________________________________

Sitz: Kurfürstenstraße 58, 45138 Essen, Deutschland
Amtsgericht Essen HRB 13615
Vorstand: Axel Deininger (Vors.), Torsten Henn, Dr. Kai Martius, Jessica Nospers
Aufsichtsratsvorsitzender: Ralf Wintergerst
______________________________________________________________________

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20241018/9580aaa3/attachment-0001.asc>