over on https://bugs.debian.org/795636, brian m. carlson describes a scenario
where gpg-agent imports an ECDSA 384-bit NIST ssh key as ssh-agent, and writes
the wrong SSH md5 fingerprint into the comment in ~/.gnupg/sshcontrol.
I've tested this and can replicate it with 2.1.7, even though the fingerprints
produced for 1024-bit RSA and 256-bit NIST ECDSA and 521-bit NIST ECDSA are both
correct. 384-bit NIST ECDSA produces a bad fingerprint.
to replicate:
------------------
export GNUPGHOME=$(mktemp -d)
echo enable-ssh-support > $GNUPGHOME/gpg-agent.conf
gpgconf --launch gpg-agent
export SSH_AUTH_SOCK=$GNUPGHOME/S.gpg-agent.ssh
for x in 256 384 521; do
ssh-keygen -t ecdsa -N '' -b $x -f testkey$x ssh-add testkey$x
done
cat $GNUPGHOME/sshcontrol
for x in 256 384 521; do
ssh-keygen -l -f testkey$x.pub
done