From: Daiki Ueno <ueno@gnu.org>
To: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
Cc: 745553@bugs.debian.org, 17338@debbugs.gnu.org,
Justus Winter <justus@g10code.com>,
rlb@defaultvalue.org, 745553-forwarded@bugs.debian.org,
Lars Ingebrigtsen <larsi@gnus.org>,
17391@debbugs.gnu.org,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
"Neal H. Walfield" <neal@walfield.org>
Subject: bug#17391: Bug#745553: emacs24-el: mml2015-always-trust should default to nil, not t
Date: Thu, 26 Jan 2017 20:34:22 +0100 [thread overview]
Message-ID: <871svpobsx.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87a8add5ye.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Thu, 26 Jan 2017 19:36:09 +0100")
Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
>> Modern versions of GnuPG automatically select the key which GnuPG knows
>> to have the best validity among all matches for the selector, thanks to
>> work put in by Justus Winter (cc'ed), so letting GnuPG make the decision
>> would relieve emacs of most of the hard work here, and would also mean
>> that any changes that the user makes to their GnuPG keyring would
>> automatically take effect in emacs without mml-mode needing to do
>> anything.
>
> The mml code is based on EasyPG by Daiki Ueno (cc’ed). EasyPG makes
> use of sub-keys and their IDs for encryption commands, instead of
> relying on GnuPG’s selections.
It was suggested by Werner to do key selection in Emacs, like GPGME. I
don't know whether GPGME changed the logic though.
>> 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.
I'm afraid I wouldn't do any work toward tofu at this level of quality;
in particular, until they reach the consensus whether tofu is only
activated when encryption is triggered by an email address.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2017-01-26 19:34 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 [this message]
2017-01-26 23:17 ` bug#17338: " Daniel Kahn Gillmor
2017-01-27 2:49 ` Daiki Ueno
2017-01-27 2:49 ` Daiki Ueno
2017-01-26 23:13 ` bug#17338: " Daniel Kahn Gillmor
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=871svpobsx.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=17338@debbugs.gnu.org \
--cc=17391@debbugs.gnu.org \
--cc=745553-forwarded@bugs.debian.org \
--cc=745553@bugs.debian.org \
--cc=dkg@fifthhorseman.net \
--cc=jens.lechtenboerger@fsfe.org \
--cc=justus@g10code.com \
--cc=larsi@gnus.org \
--cc=neal@walfield.org \
--cc=rlb@defaultvalue.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).