gpg-agent can't handle ssh & can't be adjusted
In the 3.0 Beta 1 and Alpha you could force the gpg-agent to
authenticate SSH sessions via “gpg-agent —ssh-support-enable —daemon
" '’ being the command to use authenticate the session of (like git, scp,
sshfs or ssh itself) this is useful for those who don’t want to maintain
multiple keys, for those who use OpenPGP cards for signing &
authenticating rather than persistance and for those given access to SSH
servers by their PGP public keys.
Usually a ”pkill gpg-agent" would solve the issue but now gpg-agent refuses to start with ssh-support. Adding “ssh-support-enable” to gpg-agent.conf and then “pkill gpg-agent” also does not fix this.
I don’t know what is causing the issue. I don’t know if having ssh-support on by default is a potential security issue (I’m not sure of the mechanics of turning a GPG-SSH public key back into a PGP public key) but I would like to suggest it as a solution.