I found that to use a workaround to restart gnome-keyring-daemon from command line in a way to reuse the existing socket: the env var GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring-XXXXXXXX that was previously in use.
For example:
GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/ gnome-keyring-daemon
** Message: another SSH agent is running at: /tmp/keyring-pw7JIX/ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-pw7JIX//socket
SSH_AUTH_SOCK=/tmp/keyring-pw7JIX//ssh
GNOME_KEYRING_PID=24788
When I next try to use a ssh key, it asks to authenticate again (should it?), and it caches the keyphrase again.
I found that to use a workaround to restart gnome-keyring- daemon from command line in a way to reuse the existing socket: the env var GNOME_KEYRING_ TEST_PATH. This var should be set to the /tmp/keyring- XXXXXXXX that was previously in use.
For example: TEST_PATH= /tmp/keyring- pw7JIX/ gnome-keyring- daemon pw7JIX/ ssh SOCKET= /tmp/keyring- pw7JIX/ /socket SOCK=/tmp/ keyring- pw7JIX/ /ssh PID=24788
GNOME_KEYRING_
** Message: another SSH agent is running at: /tmp/keyring-
GNOME_KEYRING_
SSH_AUTH_
GNOME_KEYRING_
When I next try to use a ssh key, it asks to authenticate again (should it?), and it caches the keyphrase again.