Yes, I know it's not perfect but when the secret key is unknown to gpg-agent then it shouldn't attempt to use it.
Feed Advanced Search
Apr 27 2017
Apr 27 2017
sa added a comment to T1967: GnuPG should select a key for signing without trying to use missing subkeys.
Mar 31 2016
Mar 31 2016
sa removed a project from T1967: GnuPG should select a key for signing without trying to use missing subkeys: Feature Request.
Mar 13 2016
Mar 13 2016
sa added a comment to T1967: GnuPG should select a key for signing without trying to use missing subkeys.
Updated patch to check that the requested key usage is SIG before checking for a
secret key.
sa added a comment to T1967: GnuPG should select a key for signing without trying to use missing subkeys.
Feb 24 2016
Feb 24 2016
sa added a comment to T1967: GnuPG should select a key for signing without trying to use missing subkeys.
Attached a patch to call agent_probe_secret_key() during finish_lookup().
This partially solves the problem by not trying to use subkeys that have no
secret key present. This does not unexpectedly change the existing behaviour
because GnuPG will currently return an error if the automatically selected
secret key is not present.
It does not solve the issue of having multiple potential signing subkeys on
different smartcards, because these are always considered to be present (if the
subkey has been associated with a smartcard).
sa added a comment to T1967: GnuPG should select a key for signing without trying to use missing subkeys.
sa set Version to 2.3.0 on T2265: SSH confirmation with gpg-agent on Windows has the Allow button as the default action.
