mutt patch: pgp-hook

pgp-hook combines various pgp-related changes

This patch has been superseded by the confirm-crypt-hook, multiple-crypt-hook, and crypt-autoselectkey patches. Please visit those pages for more details.

This patch adds two variables, pgp_autoselectkey (default no) and pgp_confirmhook (default yes).

Typical (for me) use of pgp-hook implies selection of a known key (assuming no typos), so pgp_confirmhook can be unset if you know your pgp-hooks are valid; you won't be prompted for confirmation anymore.

Similarly, it is often the case that a particular recipient (or keyID as selected via pgp-hook) results in a list of selectable keys with only one entry (not counting duplicates for uids). Setting pgp_autoselectkey will automatically select a key if only one matching (and trusted) key exists.

If multiple pgp-hooks use the same pattern, then all of the key-ids from matching patterns will be used.


This patch is available for these mutt versions:
1.5.2; 1.5.1; 1.4.1; 1.4.0; 1.3.28; 1.3.27; 1.3.26; 1.3.25; 1.2.5


2003-03-20: Patch updated for 1.4.1.

2003-01-25: Format change for 1.4i patch.

2002-12-07: Patch updated for 1.5.2.

2002-08-31: Patch updated for 1.5.1.

2002-08-25: Patch updated for 1.4i.

2002-03-13: Patch updated for 1.3.27 and 1.3.28.

2002-01-19: Patched updated for 1.3.26. In fact, aside from the PATCHES file difference, it's identical to the 1.3.25 patch.

2002-01-08: Fixed a bug where encryption to a recipient without a matching pgp-hook would silently fail and not send the message. This made the compose menu appear as if it would not respond to the send-message command (default binding 'y'). The PATCHES file is now also included in patch so that it is properly reported with the -v command-line option to mutt.

2002-01-04: You may now have multiple pgp-hook instances with the same recipient/pattern. This allows one to specify multiple keys for a particular recipient/pattern.