Re: mutt/2122: Should encrypt messages to the Sender: key as well as to recipients
On Fri, Oct 28, 2005 at 01:46:34PM -0500, Kyle Wheeler wrote:
> On Friday, October 28 at 07:13 PM, quoth New Mutt PR:
> >Currently, GPG only encrypts messages to the To:, CC: or Bcc: but *not*
> >to the From: of an email message. This means that any user that sends
> >an encrypted mail to any other user will not be able to read the e-mail
> >in the future in a default configuration (see workarounds for possible
> >ways to prevent this)
> >
> >I don't see any reason for outgoing mail to not be encrypted to the
> >sender's key so he is able to read it in the future and other software
> >(i.e. PGP Desktop) does this by default.
>
> Now, obviously, you can just add "--encrypt-to me" to the config.
>
> But in double-checking this, it occurs to me: would it be possible to
> make mutt use gpg's --hidden-recipient for bcc addresses instead of
> putting all addresses in "%r"?
This is a very interesting suggestion. It could be done by having bcc
addresses in a different % expando so they could be treated specially.
However, note that the semantics of --hidden-recipient are not exactly
the same as bcc. A user receiving a message has no idea who the bcc
recipients are - or even if there are any. A user receiving an
encrypted message with hidden recipients may not know who the hidden
recipients are, but does know they exist and how many there are.
I think the only way to maintain the same bcc semantics would be to
send a totally different message to the bcc recipients.
David