Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Angel de Vicente <angel.vicente.garrido@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Signing a message with S/MIME in Gnus?
Date: Wed, 02 Nov 2022 20:51:12 +0000	[thread overview]
Message-ID: <87leotw05b.fsf@gmail.com> (raw)
In-Reply-To: <87r0yl41ie.fsf@informationelle-selbstbestimmung-im-internet.de>

[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]

Hello,

Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:

>> 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)

I already had that, but it looks like the part it was missing was that
the certificate I was using didn't have my e-mail address, so Gnus (via
gpgsm) would not find the right certificate to use. Importing another
certificate where the e-mail address was present solved that problem.


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

That looks great, I'll have a look, becuase my SMIME setting is so far
much worse than my PGP one (my goal was to be able just to sign
messages, so I'll stop here for now, but later I want to make sure I
also get working the encryption/decryption part).

> 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...

The first certificate I was using didn't. When I used a second
certificate with the mail address in it all was good.

But here is a question. To send messages to this group I use another
e-mail address (which is not present in any of the certificates). There
is no way for me, then, to sign messages to this group with S-MIME?

I was hoping to use "Smime Keys", which according to the documentation
looks like the right way, but my attempts so far were not successful.

,----
| Show Value Smime Keys 
|    Map mail addresses to a file containing Certificate (and private key). Hide
|    The file is assumed to be in PEM format.  You can also associate additional
|    certificates to be sent with every message to each address.
`----

Thanks,
-- 
Ángel de Vicente                 -- (GPG: 0x64D9FDAE7CD5E939)
 Research Software Engineer (Supercomputing and BigData)
 Instituto de Astrofísica de Canarias (https://www.iac.es/en)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 702 bytes --]

  reply	other threads:[~2022-11-02 20:51 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
2022-11-02 20:51   ` Angel de Vicente [this message]
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=87leotw05b.fsf@gmail.com \
    --to=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).