Achtung das wird jetzt hardcore.
Das passiert wenn man bei ssh extra sicher sein will und dann gpg spielen muss:
gpg-agent -vvvv --daemon /bin/zsh
gpg-agent[440]: listening on socket '.gnupg/S.gpg-agent'
gpg-agent[440]: listening on socket '.gnupg/S.gpg-agent.extra'
gpg-agent[440]: listening on socket '.gnupg/S.gpg-agent.browser'
gpg-agent[440]: listening on socket '.gnupg/S.gpg-agent.ssh'
gpg-agent[441]: gpg-agent (GnuPG) 2.4.4 started
% ssh-add id_rsa.X
gpg-agent[441]: ssh handler 0x16b6ff000 for fd 7 started
Enter passphrase for id_rsa.X: *********
gpg-agent[441]: received ssh request of length 1873
gpg-agent[441]: ssh request handler for add_identity (17) started
gpg-agent[441]: ssh keys greater than 4096 bits are not supported
gpg-agent[441]: ssh request handler for add_identity (17) ready
gpg-agent[441]: sending ssh response of length 1
Could not add identity "id_rsa.XXXX": agent refused operation
gpg-agent[441]: ssh handler 0x16b6ff000 for fd 7 terminated
Siehe auch:
https://gnupg-users.gnupg.narkive.com/eruVL0X9/ssh-agent-keys-4096-bit
Wer ist noch dabei?