Bug#972048: Work-around
Francois Marier <[email protected]>
| Newsgroups | gmane.linux.debian.devel.ssh |
|---|---|
| Message-ID | <20201011211841.GA9617__17468.8945569628$1602451282$gmane$org@akranes.dyn.fmarier.org> |
reassign 972048 gnome-keyring
thanks
I've just realized two things:
1. The way to start ssh-agent isn't just "ssh-agent", it's actually
eval "$(ssh-agent)"
(https://unix.stackexchange.com/questions/48863/ssh-add-complains-could-not-open-a-connection-to-your-authentication-agent/48868#48868)
2. gnome-keyring-daemon is actually working, it's just no longer setting the
SSH_AUTH_SOCK environment variable for some reason. I was able to work
around this issue by adding this to my ~/.bashrc:
export SSH_AUTH_SOCK=/run/user/$(id -u)/keyring/ssh
(https://warlord0blog.wordpress.com/2020/01/29/gnome-keyring-and-ssh-agent/)
So I guess this might be from a recent GNOME change.
Francois