On Fri, Apr 18, 2025 at 04:26:36PM +0200, Antoine Le Gonidec wrote:
Since the 1:10.0p1-1 → 1:10.0p1-2 upgrade, the user socket for ssh-agent is no longer created in ${XDG_RUNTIME_DIR}/openssh_agent, but at an unpredictable path under /tmp.As an example, here is what it currently uses on my system: /tmp/ssh-EwtbKB5qzA6k/agent.3932465 (the path changes each time the ssh-agent user service is restarted) This breaks the use of commands like ssh-add, as they can no longer find the socket. This is most probably related to the fix for the following bug reports: - https://bugs.debian.org/961311 - https://bugs.debian.org/1039919 - https://bugs.debian.org/1103037 For now it can be worked around by downgrading openssh-client to the Trixie version (1:9.9p2-2), and open the socket with: /usr/lib/openssh/agent-launch start
Surprising, since the systemd unit uses ListenStream=%t/openssh_agent and sets SSH_AUTH_SOCK in the systemd environment. Daniel, could you please have a look at this, since it was your change?
Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
