Page MenuHome GnuPG

Prefer keys with no or cached passphrase.
Closed, DuplicatePublic


gpg should prefer keys with no or a cached passphrase, when decrypting a message.

Event Timeline

I have a possible solution pushed to branch justus/issue1955. The idea is to try
to parse the message with PINENTRY_MODE_CANCEL first, and should that fail, we
retry with the configured pinentry mode. Not sure if that is too hacky, or what
side-effects parsing the message may have that we must not do twice. Werner,
what do you think?

werner edited projects, added gnupg (gpg23); removed gnupg, gnupg (gpg21).