Re: mutt/2122: Should encrypt messages to the Sender: key as well as to recipients
The following reply was made to PR mutt/2122; it has been noted by GNATS.
From: Paul Walker <paul@xxxxxxxxxxxxxxxxxxxxx>
To: Javier Fern?ndez-Sanguino Pe?a <jfs@xxxxxxxxxxxx>
Cc: bug-any@xxxxxxxxxxxxx, mutt-dev@xxxxxxxx
Subject: Re: mutt/2122: Should encrypt messages to the Sender: key as well as
to recipients
Date: Fri, 28 Oct 2005 18:47:33 +0100
--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 28, 2005 at 07:40:13PM +0200, Javier Fern?ndez-Sanguino Pe?a wr=
ote:
> > Which is fine, but from a quick glance at your patch, I couldn't see ho=
w you
> > disable this. The user needs to be able to turn this off, if it's there.
> There's no way. Just like there is no current way to disable encrypting to
> Bcc or CC: :-)
The difference is that Cc and Bcc don't intrinsically leave a copy of the
message in more or less the same place as the key. ;-)
In addition, if your patch is applied, the user has no way to make sure that
they cannot produce a record of the email's contents.
--=20
Paul
Now I have visions of engines mounted at 45 degree angles to the (normal)
direction of travel of the car. Because, you know, 90 degree angles cause
bad ch'i and all that. -- Logan Shaw
--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDYmQ1P9fOqdxRstoRApB4AJ4ua6VmN9KzL3upYMpP+l2TI+3kcwCffZsJ
ZrfdmnfNrjM1gSwfXtXg204=
=yK6V
-----END PGP SIGNATURE-----
--y0ulUmNC+osPPQO6--