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: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <jfs@xxxxxxxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc:
Subject: Re: mutt/2122: Should encrypt messages to the Sender: key as well as
to recipients
Date: Sat, 26 Nov 2005 20:58:10 +0100
--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 25, 2005 at 10:51:53PM +0100, Alain Bench wrote:
> Synopsis: Should encrypt messages to the Sender: key as well as to recipi=
ents
>=20
> **** Comment added by ab on Fri, 25 Nov 2005 22:51:53 +0100 ****
> =20
> Thanks Javier. It seems to me that all 3 of encrypting
> to sender, to a special storage key, or to no self, are
> valid expectations: User should have the choice. He should
> also have the choice to hide his keyid. All this can be done
> in options to $pgp_encrypt(_sign)_command, but I agree it's
> not very practical, especially in dynamic configs, even more
> in PGP/GPG heterogenous installations.
Ok.
> So a way to set self-encryption easely would be usefull.
> But it has to be configurable, and I agree with Michael that
I don't understand why it needs to be configurable and signing for Bcc is
not.
> for security reason the default should be no self, as today.
For what "security reasons"? If you want to mention privacy (or protection
=66rom legal action), fine, but for "availability" (which is a security
concept) users would expect to have their saved mail encrypted against their
private key so that they are able to read it in the future. Not doing it
makes mutt fail the "principle of least astonishment", most people
will think that the mail will sent will be readable after for them, however,
it it will not. I've personally seen this mistake a few times on several
people that use mutt (me included) and I bet there are lots others.
As I said in my report, the default behaviour for other mail encryption
software (such as PGP) is to encrypt with your private key per default. I
suggest that be the default too for mutt.
Regards
Javier
--5vNYLRcllDrimb99
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)
iD8DBQFDiL5RsandgtyBSwkRAtaaAJ44JE5cvQicjXuorr4/IbRAavjnMQCfbMlP
635oPZm0iPDLhfmxTxZyTk0=
=9uQa
-----END PGP SIGNATURE-----
--5vNYLRcllDrimb99--