<<< Date Index >>>     <<< Thread Index >>>

Re: How does mutt know which key to use to encrypt to the sender?



On Thu, Apr 01, 2004 at 11:49:28PM +0200, René Clerc muttered:
> * Charles Curley <charlescurley@xxxxxxxxxxxxxxxxx> [01-04-2004 23:30]:
> 
> > Let me ask a related question: How does mutt know which key to use to
> > encrypt (not sign) to the sender?
> 
> Mutt simply calls what's in your $pgp_encrypt_(sign|only)_command.

Right, which are:

set pgp_encrypt_only_command="pgpewrap gpg -v --batch -o - --encrypt --textmode 
--armor --always-trust -- -r %r -- %f"
set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch -o - 
--encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"

At the top of the file gpg.rc the notes indicate that %r is a list of
key IDs. So the key IDs are coming from somewhere else.

> Also, gnupg has an option 'encrypt-to', which you can use to specify
> additional keys to encrypt to.

As far as I can tell, I'm not using encrypt-to. In fact, it isn't in
the manual for the version I have.

I have mutt-1.4.1-5. The current version is 1.4.2.1, but I don't want
to upgrade unless I can get a Fedora 1 compilant RPM. From the release
notes, there should not be any changes in 1.4.2 that affect this
issue.

To find out whether I am using encrypt-to or other key words, I
grepped for "source' in .muttrc, and constructed a grep on the results
of the first grep.


-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Attachment: pgp27NjckFHUn.pgp
Description: PGP signature