Page MenuHome GnuPG
Create Task
Maniphest T1955

Prefer keys with no or cached passphrase.
Closed, DuplicatePublic
Actions

Description

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

Event Timeline

Mento added a project: Feature Request.Apr 19 2015, 2:57 PM
Mento added a subscriber: Mento.
• werner added projects: gnupg (gpg21), gnupg.Jun 8 2015, 8:03 PM
• werner added a subscriber: • werner.Jun 9 2015, 10:06 AM

This also extends to keys stored on smartcards, see
https://lists.gnupg.org/pipermail/gnupg-devel/2015-June/029959.html

guido added a subscriber: guido.Mar 30 2016, 5:31 PM
justus added a subscriber: justus.Jul 25 2016, 10:52 AM

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 moved this task from gpg21 to gpg23 on the gnupg board.Oct 20 2017, 1:56 PM
• werner edited projects, added gnupg (gpg23); removed gnupg, gnupg (gpg21).
• werner closed this task as a duplicate of T3119: gpg: Improve public key decryption.Oct 20 2017, 1:58 PM