Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: Angel de Vicente <angel.vicente.garrido@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Signing a message with S/MIME in Gnus?
Date: Wed, 02 Nov 2022 20:09:13 +0100	[thread overview]
Message-ID: <87r0yl41ie.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <871qql9021.fsf@gmail.com> (Angel de Vicente's message of "Wed, 02 Nov 2022 09:29:26 +0000")

Hi there!

On 2022-11-02, at 09:29, Angel de Vicente wrote:

> Hello,
>
> anyone here familiar with Gnus + S/MIME + gnupg?

Yes :)

> [...]
> But when I try to sign a message from Gnus I always get a message saying
> "No sign key for <angel.de.vicente@iac.es>; skip it? (y or n)"

I use this:
(setq mml-secure-smime-sign-with-sender t)

And more: https://gitlab.com/lechten/defaultencrypt

> What do I have to configure in Emacs/Gnus so that it will know that my
> e-mail address is linked to the same certificate used in the command
> line?

Your CA links your e-mail address to your public key, both of which
are recorded inside the certificate.  Gnus cannot do this.  Your
output did not show whether the certificate really contains the
e-mail address that you used...

Best wishes
Jens


  reply	other threads:[~2022-11-02 19:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  9:29 Angel de Vicente
2022-11-02 19:09 ` Jens Lechtenboerger [this message]
2022-11-02 20:51   ` Angel de Vicente
2022-11-03  7:09     ` Jens Lechtenboerger
2022-11-03  7:21       ` Angel de Vicente
2022-11-03 15:28         ` Angel de Vicente
2022-11-03 17:52           ` GH
2022-11-03 18:32             ` Angel de Vicente
2022-11-04 18:11           ` Angel de Vicente
2022-11-03 18:55         ` Jens Lechtenboerger
2022-11-03 19:25           ` Emanuel Berg

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=87r0yl41ie.fsf@informationelle-selbstbestimmung-im-internet.de \
    --to=jens.lechtenboerger@fsfe.org \
    --cc=angel.vicente.garrido@gmail.com \
    --cc=info-gnus-english@gnu.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.
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 NNTP newsgroup(s).