I'm trying to sign someone's GPG key, and keep getting a strange error:
# for example$ gpg --sign-key cfeck@kde.org pub rsa2048/DBD2CE893E2D1C87 created: 2017-06-27 expires: never usage: SC trust: unknown validity: unknownsub rsa2048/C714D46F0AB88BAA created: 2017-06-27 expires: never usage: E [ unknown] (1). Christoph Feck <cfeck@kde.org>gpg: using "5F6E4C40D1D8450B" as default secret key for signingpub rsa2048/DBD2CE893E2D1C87 created: 2017-06-27 expires: never usage: SC trust: unknown validity: unknown Primary key fingerprint: F232 75E4 BF10 AFC1 DF69 14A6 DBD2 CE89 3E2D 1C87 Christoph Feck <cfeck@kde.org>Are you sure that you want to sign this key with yourkey "Caleb Xavier Berger (Master Hardware Key) <caleb.x.berger@gmail.com>" (5F6E4C40D1D8450B)Really sign? (y/N) ygpg: signing failed: No secret keygpg: signing failed: No secret keyKey not changed so no update needed.But I can run commands like gpg --sign just fine, and get signed messages as you would expect from that:
$ gpg --sign --armorgpg: using "5F6E4C40D1D8450B" as default secret key for signingmemes!-----BEGIN PGP MESSAGE-----owGbwMvMwCG29qzhPD2zoGLG07xJDMlt091zU3NTixW5OkpZGMQ4GGTFFFlSpYV77ny+uvHfx612MOWsTEC1PgxcnAIwkUNmDP/UOBcekTt6v2qurMVGg5cf16QsjytqaXRKYGj8sT8vZ0IkI8N/u85nUy5s83SZ0cesEB/2LOfA3ZWNMx5ucKpd9okrazczAA===/7Ap-----END PGP MESSAGE-----In case it's relevant, my secret key is stored on a YubiKey that I have plugged in throughout. It shows up fine with gpg --list-secret-keys and gpg --card-edit appears to be working correctly as well.
What's different about keysigning that might be breaking things?
