From: Lars Ingebrigtsen <larsi@gnus.org>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: 26587@debbugs.gnu.org
Subject: bug#26587: 26.0.50; Gnus signs with false S/MIME key
Date: Wed, 09 Oct 2019 21:59:34 +0200 [thread overview]
Message-ID: <87sgo14rmh.fsf@gnus.org> (raw)
In-Reply-To: <87pnj6s3bj.fsf@physik.rwth-aachen.de> (Torsten Bronger's message of "Wed, 9 Oct 2019 10:58:24 +0200")
Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
> When writing the message, I call (mml-secure-message-sign-smime).
> The "From:" field contains "Torsten Bronger
> <bronger@physik.rwth-aachen.de>". My secret keys are:
OK, my first attempt at this ended up with Message not complaining at
all, but sending out a "signed" message with the following empty
signature:
--=-=-=
Content-Type: application/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=smime.p7s
--=-=-=--
I've now made it bug out if it can't find any identity to sign with.
Now, for the bug you're seeing... If I'm tracing the code right (and I
may well not be), this is what's used to find what name to sign with:
(defun mml-secure-signer-names (protocol sender)
"Determine signer names for PROTOCOL and message from SENDER.
Returned names may be e-mail addresses or key IDs and are determined based
on `mml-secure-openpgp-signers' and `mml-secure-openpgp-sign-with-sender' with
OpenPGP or `mml-secure-smime-signers' and `mml-secure-smime-sign-with-sender'
with S/MIME."
(if (eq 'OpenPGP protocol)
(append mml-secure-openpgp-signers
(if (and mml-secure-openpgp-sign-with-sender sender)
(list (concat "<" sender ">"))))
(append mml-secure-smime-signers
(if (and mml-secure-smime-sign-with-sender sender)
(list (concat "<" sender ">"))))))
mml-secure-smime-sign-with-sender defaults to nil, so it's normally not
used. So this returns just the value of mml-secure-smime-signers.
What's that variable for you?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-09 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 11:41 bug#26587: 26.0.50; Gnus signs with false S/MIME key Torsten Bronger
2019-09-27 15:32 ` Lars Ingebrigtsen
2019-10-09 8:58 ` Torsten Bronger
2019-10-09 19:59 ` Lars Ingebrigtsen [this message]
2019-10-10 7:43 ` Torsten Bronger
2019-10-11 7:29 ` Lars Ingebrigtsen
2020-08-04 9:04 ` Lars Ingebrigtsen
2020-08-04 10:10 ` Robert Pluim
2020-08-04 10:31 ` Lars Ingebrigtsen
2019-10-09 20:42 ` Lars Ingebrigtsen
2019-10-10 6:55 ` Torsten Bronger
2019-10-11 7:29 ` 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=87sgo14rmh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26587@debbugs.gnu.org \
--cc=bronger@physik.rwth-aachen.de \
/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).