all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 22:42:21 +0200	[thread overview]
Message-ID: <87pnj53b2q.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:

> I would like the second key to be used.  But Gnus signs the email
> with the first certificate.

If I understand the code correctly, `epg-start-sign' is run here, and
gpgsm is started with the parameters looking like 

"--detach-sign" "-u" "4A44812B553ACE6D" "-u" "4A44812B553ACEetc"

with as many "-u"s as there are in your gpgsm store that matches
whatever you've set up in that list that lists all your identities you
want to use.

Could you edebug that function to see if that's really what happens?
Because if it is, we're leaving the decision to gpgsm itself which user
ID to use, and that seems very sub-optimal.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-10-09 20:42 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnj53b2q.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.