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

Re: [Mutt] #2122: Should encrypt messages to the Sender: key as



#2122: Should encrypt messages to the Sender: key as well as to recipients
-------------------------------+--------------------------------------------
  Reporter:  jfs@xxxxxxxxxxxx  |       Owner:  mutt-dev
      Type:  enhancement       |      Status:  new     
  Priority:  trivial           |   Milestone:          
 Component:  crypto            |     Version:          
Resolution:                    |    Keywords:  patch   
-------------------------------+--------------------------------------------
Changes (by pdmef):

  * component:  mutt => crypto


Old description:

> {{{
> 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.
>
> I suggest the attached (tested) patch be introduced to mutt to introduce
> this new behavior.
> >How-To-Repeat:
> Send a PGP/GPG encrypted mail to someone (without having 'encrypt-to'
> with your own GPG key in the gnupg.options file) and try to open the mail
> saved on the folder
> >Fix:
> The current work around to this issue is either adding 'encrypt-to
> YourKeyID' in gnupg.options or e-mailing to yourself (in Bcc: or To:) so
> that either a) gnupg encrypts to you by default or b) mutt tells gnupg to
> encrypt to you (adds you to the keylist)
> }}}

New description:

 {{{
 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.

 I suggest the attached (tested) patch be introduced to mutt to introduce
 this new behavior.
 >How-To-Repeat:
 Send a PGP/GPG encrypted mail to someone (without having 'encrypt-to' with
 your own GPG key in the gnupg.options file) and try to open the mail saved
 on the folder
 >Fix:
 The current work around to this issue is either adding 'encrypt-to
 YourKeyID' in gnupg.options or e-mailing to yourself (in Bcc: or To:) so
 that either a) gnupg encrypts to you by default or b) mutt tells gnupg to
 encrypt to you (adds you to the keylist)
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2122#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent