David Rock wrote:
> Try just hitting the enter key when prompted for a key. It should
> display _ALL_ the keys you currently have defined. You can just pick
> the one you want from the list.
I rarely use this feature, but I have on occasion and I always
wondered why mutt presented you with a list of all the keys on your
public keyring when you hit enter at the "Sign as:" prompt. Aren't
the odds of being able to sign a message with most of the keys on the
pubring pretty low? It would seem better to select from the secret
keyring. Taking a quick poke at the source for 1.5.4, compose.c could
be changed simply to achieve this I think. Anyone familiar with the
mutt code see a reason not to apply a patch like the one below? Is
KEYFLAG_CANSIGN supposed to weed out all the keys on the pubring that
can't sign? If so, that's not working for me with mutt 1.5.4, gnupg
1.2.3, and the gpg.rc from mutt's contrib dir.
--- compose.c~ Mon Oct 27 22:26:09 2003
+++ compose.c Mon Oct 27 22:26:18 2003
@@ -188,7 +188,7 @@
unset_option(OPTPGPCHECKTRUST);
if ((p = crypt_pgp_ask_for_key (_("Sign as: "), NULL,
- KEYFLAG_CANSIGN, PGP_PUBRING)))
+ KEYFLAG_CANSIGN, PGP_SECRING)))
{
snprintf (input_signas, sizeof (input_signas), "0x%s",
crypt_pgp_keyid (p));
--
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
Always do right -- this will gratify some and astonish the rest.
-- Mark Twain (1835-1910)
Attachment:
pgpOSTdkhnzX3.pgp
Description: PGP signature