all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be>
Cc: "36222@debbugs.gnu.org" <36222@debbugs.gnu.org>
Subject: bug#36222: 26.1; Message sent even with invalid S/MIME password
Date: Fri, 18 Oct 2019 05:31:16 +0200	[thread overview]
Message-ID: <871rvalofv.fsf@gnus.org> (raw)
In-Reply-To: <87sgnryqli.fsf@poincare.umons.ac.be> (Christophe TROESTLER's message of "Thu, 17 Oct 2019 22:06:20 +0000")

Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be> writes:

>> How do you ask Message to send with S/MIME?  Using the `C-c C-m C s'
>> command?
>
> Yes.
>
>> And how do you set up the S/MIME recipient stuff?
>
> My config :
>
> (setq mml-smime-use 'epg)
> (setq mm-decrypt-option 'always)
> (setq mm-verify-option 'always)
> (setq gnus-buttonized-mime-types '("multipart/encrypted" "multipart/signed"))
>
> Then use gpgsm to import your certificate (delivered by a certificate
> authority).

Hm...  when I do this, Message creates a 

 Content-Type: application/pkcs7-mime;
  smime-type=enveloped-data;
  name=smime.p7m

message (without prompting me for a password, which is strange), and
when I decrypt it, I'm then prompted for a password, and then it's
decrypted successfully.

I thought I needed my private key when sending, but apparently not.  Hm.

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





  reply	other threads:[~2019-10-18  3:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15  9:21 bug#36222: 26.1; Message sent even with invalid S/MIME password Christophe TROESTLER
2019-09-22 21:50 ` Lars Ingebrigtsen
2019-10-17 22:06   ` Christophe TROESTLER
2019-10-18  3:31     ` Lars Ingebrigtsen [this message]
2019-10-18  3:39       ` Lars Ingebrigtsen
2020-03-30  6:47         ` Christophe Troestler
2020-08-03  7:50           ` 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=871rvalofv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36222@debbugs.gnu.org \
    --cc=Christophe.TROESTLER@umons.ac.be \
    /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.