On Mon 2025-03-31 21:53:41 +0200, Marc Haber wrote: > It is probably enough to have an ssh-agent running on the side of the > ssh client to invoke a gpg agent on the server side? I am not using gpg > in any way here.
If we were to remove the systemd sockets, then gpg would auto-launch the daemons on its own. So maybe the issue is that the gpg-agent-ssh.socket startup is somehow setting SSH_AUTH_SOCK when it shouldn't be? Marc, what does this command show for you? gpgconf --list-options gpg-agent | grep ^enable-ssh-agent: Can you see anything in the per-user journal for the system user related to gpg-agent? as the system user in question, can you share the output of this: journalctl --user-unit 'gpg-agent*' Regards, --dkg
signature.asc
Description: PGP signature