From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Default encryption for Message
Date: Tue, 23 Sep 2014 16:02:00 -0400 [thread overview]
Message-ID: <m2siji9kcn.fsf@lifelogs.com> (raw)
In-Reply-To: <86wq8xffpv.fsf@informationelle-selbstbestimmung-im-internet.de>
On Sun, 21 Sep 2014 12:08:44 +0200 Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> wrote:
JL> 1. Bcc handling.
JL> Bcc handling in Gnus is broken. Messages are encrypted to
JL> all recipients, giving away the key IDs (thus, in general the
JL> identities) of all recipients, including the “blind” ones.
JL> The Right Thing is explained there:
JL> http://lists.gnupg.org/pipermail/gnupg-users/2014-April/049394.html
JL> In DefaultEncrypt I added a test to warn against such cases. In the
JL> version linked above, mml-secure-bcc-is-safe implements that test.
JL> I suggest to copy that function (and its prerequisites) into
JL> mml-sec.el. Then, mml-secure-bcc-is-safe can be added as
JL> message-send-hook, which I suggest as default until proper Bcc
JL> handling is implemented.
I don't think warning is enough. If it can be fixed, it should be fixed.
JL> 2. mml-default-encrypt-method
No opinion.
JL> 3. Creation of signatures
...
JL> I’m not sure about user expectations and the necessity of backwards
JL> compatibility, though.
No opinion, except IMO the Right Thing should override backwards
compatibility when it comes to security.
JL> 4. mm-encrypt-option
...
JL> Clearly, my [solution] is a hack. A better approach might be a third
JL> value for mm-encrypt-option, say guided-if-multiple, to only enter
JL> guided mode if multiple keys are available. That would require,
JL> however, to modify code in mml1991.el, mml2015.el, and mml-smime.el,
JL> which brings me to the next point.
Ask once, then save the preference in a Customize-controlled variable.
JL> 5. Refactoring
No opinion.
Ted
next prev parent reply other threads:[~2014-09-23 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 10:08 Jens Lechtenboerger
2014-09-23 20:02 ` Ted Zlatanov [this message]
2014-09-24 13:59 ` Jens Lechtenboerger
2014-09-24 15:28 ` Ted Zlatanov
2014-09-24 2:23 ` Daiki Ueno
2014-09-24 14:30 ` Jens Lechtenboerger
2014-09-25 3:06 ` Daiki Ueno
2014-09-25 16:18 ` Jens Lechtenboerger
2014-09-28 0:16 ` Daiki Ueno
2014-10-02 16:51 ` Jens Lechtenboerger
2015-10-16 16:26 ` Refactoring of mml1991.el, mml2015.el, mml-smime.el (was: Default encryption for Message) Jens Lechtenboerger
2015-10-18 7:36 ` Refactoring of mml1991.el, mml2015.el, mml-smime.el Peter Münster
2015-10-18 14:09 ` Greg Troxel
2015-10-19 12:58 ` Jens Lechtenboerger
2015-11-06 2:10 ` Daiki Ueno
2015-11-07 20:28 ` Jens Lechtenboerger
2015-11-11 6:20 ` Daiki Ueno
2015-11-14 15:44 ` Jens Lechtenboerger
2015-11-20 16:31 ` in defense of GitLab or something (was: Refactoring of mml1991.el, mml2015.el, mml-smime.el) Ted Zlatanov
2014-09-22 12:49 Default encryption for Message Uwe Brauer
2014-09-22 17:04 ` Jens Lechtenboerger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2siji9kcn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).