I see something interesting :
"env" command outputs some nice thing, especially :
[gnome-terminal launched through menu]
GNOME_KEYRING_SOCKET=/tmp/keyring-mNji2A/socket
SSH_AUTH_SOCK=/tmp/keyring-mNji2A/socket.ssh
[gnome-terminal launched through gmrun]
GNOME_KEYRING_SOCKET=/tmp/keyring-mNji2A/socket
SSH_AUTH_SOCK=/tmp/ssh-gvpqNC5125/agent.5125
shouldn't SSH_AUTH_SOCK be the same ?!
When launching a second terminal through the menu, it shows me that it's using the same agent [that's logical...]
so, question is : why is it using a second, unknown agent when it's launched through another mean ??
I see something interesting :
"env" command outputs some nice thing, especially :
[gnome-terminal launched through menu] SOCKET= /tmp/keyring- mNji2A/ socket SOCK=/tmp/ keyring- mNji2A/ socket. ssh
GNOME_KEYRING_
SSH_AUTH_
[gnome-terminal launched through gmrun] SOCKET= /tmp/keyring- mNji2A/ socket SOCK=/tmp/ ssh-gvpqNC5125/ agent.5125
GNOME_KEYRING_
SSH_AUTH_
shouldn't SSH_AUTH_SOCK be the same ?!
When launching a second terminal through the menu, it shows me that it's using the same agent [that's logical...]
so, question is : why is it using a second, unknown agent when it's launched through another mean ??