From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: stepnem@gmail.com, 40118@debbugs.gnu.org, boudiccas@skimble.plus.com
Subject: bug#40118: 27.0.90; Signing emails with gpg
Date: Thu, 30 Apr 2020 09:37:58 +0200 [thread overview]
Message-ID: <m2tv11todl.fsf@gmail.com> (raw)
In-Reply-To: <87r1w5384c.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 30 Apr 2020 06:33:39 +0200")
>>>>> On Thu, 30 Apr 2020 06:33:39 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Robert Pluim <rpluim@gmail.com> writes:
>> I donʼt know. Lars? (and why only for signing and not encrypting?)
>>
>> commit 9c81149ae9165b0f017d60d141221b340879baef
>> Author: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Wed Oct 9 21:55:41 2019 +0200
>>
>> Make mml-secure-epg-sign bug out if we can't find an identity
>>
>> * lisp/gnus/mml-sec.el (mml-secure-epg-sign): Bug out if we
>> couldn't find anything to sign with instead of silently pretending
>> to sign.
Lars> It's odd that the commit isn't tied to a bug report, because I remember
Lars> twiddling with this stuff as a result of a report?
Lars> Anyway, I think it's correct to bug out here if we can't find a signer,
Lars> but the error message is, as you note, somewhat wrong.
I donʼt think itʼs correct: previous to this change, telling gnus to
sign an email would result in gpg using your default key, which in 99%
of the cases is the right thing to do. The 1% know how to override it.
Hence my strong desire to set
mml-secure-{smime,openpgp}-sign-with-sender to t. Or do the query
thing I proposed a patch for earlier. Or update the message.
In that order of preference, I think.
Lars> I think. As you note, it's odd that it's only doing this when signing
Lars> and not encrypting.
Thatʼs a separate issue. And proobably only affects 1% of the 1% :-)
Robert
next prev parent reply other threads:[~2020-04-30 7:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:51 bug#40118: 27.0.90; Signing emails with gpg Sharon Kimble
2020-04-14 11:10 ` Štěpán Němec
2020-04-15 16:37 ` Robert Pluim
2020-04-15 16:45 ` Eli Zaretskii
2020-04-16 9:44 ` Robert Pluim
2020-04-16 10:15 ` Eli Zaretskii
2020-04-16 10:38 ` Robert Pluim
2020-04-17 15:11 ` Robert Pluim
2020-04-20 10:52 ` Robert Pluim
2020-04-20 16:24 ` Eli Zaretskii
2020-04-20 16:58 ` Robert Pluim
2020-04-30 4:33 ` Lars Ingebrigtsen
2020-04-30 7:37 ` Robert Pluim [this message]
2020-04-30 22:03 ` Lars Ingebrigtsen
2020-05-05 12:46 ` Robert Pluim
2020-05-05 15:06 ` Eli Zaretskii
2020-05-05 15:23 ` Robert Pluim
2020-05-05 16:07 ` Eli Zaretskii
2020-09-30 14:57 ` Lars Ingebrigtsen
2020-09-30 16:44 ` Robert Pluim
2020-10-01 0:16 ` Lars Ingebrigtsen
2020-10-01 17:41 ` Robert Pluim
2020-10-01 17:43 ` Lars Ingebrigtsen
2020-10-02 8:49 ` Robert Pluim
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=m2tv11todl.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=40118@debbugs.gnu.org \
--cc=boudiccas@skimble.plus.com \
--cc=larsi@gnus.org \
--cc=stepnem@gmail.com \
/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).