From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
Cc: 745553@bugs.debian.org, 17338@debbugs.gnu.org,
Justus Winter <justus@g10code.com>,
745553-forwarded@bugs.debian.org,
Lars Ingebrigtsen <larsi@gnus.org>, Daiki Ueno <ueno@gnu.org>,
17391@debbugs.gnu.org, rlb@defaultvalue.org,
"Neal H. Walfield" <neal@walfield.org>
Subject: bug#17338: bug#17391: Bug#745553: emacs24-el: mml2015-always-trust should default to nil, not t
Date: Thu, 26 Jan 2017 18:13:50 -0500 [thread overview]
Message-ID: <87k29h2z4h.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <87a8add5ye.fsf@informationelle-selbstbestimmung-im-internet.de>
On Thu 2017-01-26 13:36:09 -0500, Jens Lechtenboerger wrote:
> On 2017-01-25, at 15:30, Daniel Kahn Gillmor wrote:
>> On Wed 2017-01-25 15:09:47 -0500, Jens Lechtenboerger wrote:
>>> mml2015-always-trust is replaced by mml-secure-openpgp-always-trust
>>> nowadays. I certainly wouldn’t object if the default value was
>>> changed, but lots of long-term users might be surprised.
>>
>> It's also possible that lots of long-term users might be surprised to
>> find that refreshing one key in their keyring is likely to cause a
>> change in behavior for the use of other keys in their keyring. this is
>> a silent surprise, which seems worse than a public surprise.
>
> Sorry, I don’t understand this. What change in one key is causing
> silent changes for other keys?
Without the notification that multiple keys are available, Bob can add
Carol's User ID to his cert ; depending on where the certs are
positioned linearly in Alice's keyring, mail to Carol might be encrypted
to Bob's key, or to Alice's key.
I think this is mitigated at least in part by prompting the user when
there are multiple keys available, though.
> That’s customized in mml-secure-key-preferences. So, the usual
> customize interface is available. And there is some code to detect
> and remove unusable customizations.
When was this introduced? i don't see it, but then i'm still using
emacs24. Do i need to upgrade?
>> Modern versions of GnuPG also provide a "tofu" mechanism to store and
>> track that kind of decision in. Neal Walfield (also cc'ed here) put in
>> a lot of that implementation, so he might have some suggestions for the
>> best way to handle it.
>
> If Emacs was relying on GnuPG’s decisions, nothing special would be
> necessary for tofu, right? (Users could activate that in their
> gpg.conf.)
Neal can answer this better than i can. I think the TOFU mode works
best when there's a bit of UI integration -- emacs would provide the way
for the user to answer a question prompted by gpg, and then gpg is
responsible for storing/tracking all the info.
--dkg
next prev parent reply other threads:[~2017-01-26 23:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140422190613.18043.21415.reportbug@alice.fifthhorseman.net>
2014-04-24 19:12 ` Bug#745553: emacs24-el: mml2015-always-trust should default to nil, not t Rob Browning
2014-05-02 20:29 ` Daniel Kahn Gillmor
2017-01-25 17:19 ` bug#17391: " Lars Ingebrigtsen
2017-01-25 20:09 ` bug#17338: " Jens Lechtenboerger
2017-01-25 20:30 ` Daniel Kahn Gillmor
2017-01-26 18:36 ` Jens Lechtenboerger
2017-01-26 19:34 ` Daiki Ueno
2017-01-26 23:17 ` bug#17338: " Daniel Kahn Gillmor
2017-01-27 2:49 ` Daiki Ueno
2017-01-27 2:49 ` bug#17338: " Daiki Ueno
2017-01-26 23:13 ` Daniel Kahn Gillmor [this message]
2017-01-27 6:45 ` Jens Lechtenboerger
2017-01-26 23:19 ` Daniel Kahn Gillmor
2022-02-20 13:11 ` bug#17338: " Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k29h2z4h.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=17338@debbugs.gnu.org \
--cc=17391@debbugs.gnu.org \
--cc=745553-forwarded@bugs.debian.org \
--cc=745553@bugs.debian.org \
--cc=jens.lechtenboerger@fsfe.org \
--cc=justus@g10code.com \
--cc=larsi@gnus.org \
--cc=neal@walfield.org \
--cc=rlb@defaultvalue.org \
--cc=ueno@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).