Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: S/MIME + additional certificate files
Date: Mon, 23 Sep 2002 17:58:23 +0200	[thread overview]
Message-ID: <ilusn00aeao.fsf@latte.josefsson.org> (raw)
In-Reply-To: <iluy99saek1.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 23 Sep 2002 17:52:46 +0200")

Simon Josefsson <jas@extundo.com> writes:

> The sign command only need the key to sign something.  By reading the
> OpenSSL S/MIME man page it seems that -certfile should be specified to
> solve this problem.  What does the following do?  (Untested, it might
> mail your private key...)

Never mind that bogus patch, what you suggested seem to be The Right
Thing, and from what I could tell it was a complete solution as well
(only signing needs extra user certs, and you fixed that).  Committed.
If you send more patches, you must sign FSF papers.




  reply	other threads:[~2002-09-23 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 14:46 Krzysztof Jędruczyk
2002-09-23 15:52 ` Simon Josefsson
2002-09-23 15:58   ` Simon Josefsson [this message]
2002-09-23 16:58     ` Krzysztof Jędruczyk

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=ilusn00aeao.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.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).