From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: emacs-devel@gnu.org
Cc: Damien Cassou <damien@cassou.me>,
Gregor Zattler <telegraph@gmx.net>,
Nicolas Petton <nicolas@petton.fr>
Subject: Re: [Emacs-diffs] master 29006a6: Detect if a message can be encrypted and add an MML tag
Date: Wed, 11 Apr 2018 20:00:27 +0200 [thread overview]
Message-ID: <87po35ipxg.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <mailman.37408.1523451062.27992.emacs-devel@gnu.org> (emacs-devel-request's message of "Wed, 11 Apr 2018 08:51:02 -0400")
>> 1) It adds the MML tags even if the recipients key is disabled.
>
>
> I don't know what "the recipients key is disabled" means.
Function mml-secure-check-sub-key avoids disabled keys,
mml-secure-find-usable-keys calls that. You may want to call the
latter instead of epg-list-keys. That’s what I do in jl-encrypt.el
[1].
>> 2) More complicated: The UI does not provide a means to
>> temporarily not use encryption [...]
>
> I agree. We could add a boolean buffer-local variable that the user
> could toggle with something like `M-x
> message-toggle-sign-encrypt-if-all-keys-available`. This would only
> affect the current buffer. What do you think?
In jl-encrypt.el the user can confirm that they really want to send
plaintext although keys are available.
Best wishes
Jens
[1] https://www.informationelle-selbstbestimmung-im-internet.de/Emacs.html
next parent reply other threads:[~2018-04-11 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.37408.1523451062.27992.emacs-devel@gnu.org>
2018-04-11 18:00 ` Jens Lechtenboerger [this message]
[not found] <20180404183303.27542.7640@vcs0.savannah.gnu.org>
[not found] ` <20180404183305.17AB4202C3@vcs0.savannah.gnu.org>
2018-04-11 11:32 ` [Emacs-diffs] master 29006a6: Detect if a message can be encrypted and add an MML tag Gregor Zattler
2018-04-11 11:44 ` Damien Cassou
2018-04-11 13:07 ` Herring, Davis
2018-04-11 17:57 ` Gregor Zattler
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=87po35ipxg.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--cc=damien@cassou.me \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
--cc=telegraph@gmx.net \
/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).