On my Gnome system i start ssh-agent and set $SSH_AUTH_SOCK via a --user systemd service like this:
[Unit]
Description=SSH key agent
[Service]
Type=simple
Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket
# DISPLAY required for ssh-askpass to work
Environment=DISPLAY=:0
ExecStart=/usr/bin/ssh-agent -D -a $SSH_AUTH_SOCK
[Install]
WantedBy=default.target
After login to Gnome, it autostarts KeepassXC and in that, i could make use of $SSH_AUTH_SOCK and use the SSH-Agent integration. Since the update this week, this integration isn’t working anymore as expected. KeepassXC complains that no ssh-agent is executed.
If i open a console and check the systemd service, i see it enabled and active. If i use printenv | grep SSH_AUTH_SOCK on the same console it prints the expected var and path. If i start KeepassXC again from the Gnome Arch menu or Dock, the ssh-agent integration is not working. But when i start keepassxc from the same console as where i check the env var, the integration works.
I get the same behaviour for all other applications which make use of $SSH_AUTH_SOCK.
Any idea, what’s wrong after the update or how to solve this?
in your ~/.pam_environment? It’s not evaluated any more since the last update (deprecated). Take a look at AUR (en) - systemd-ssh-agent how to set this at another place.
If you dont want to install the AUR package, you can create the shell script and insert, the content by yourself. You must do that with root privileges. For example on the shell: