From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: signing and encrypting with new <#secure> tag
Date: Tue, 16 Apr 2002 18:25:09 -0400 [thread overview]
Message-ID: <87sn5v8enu.fsf@alum.wpi.edu> (raw)
In-Reply-To: <m1bofgjwla0.fsf@blackbird.mitre.org>
david.goldberg6@verizon.net (David S. Goldberg) writes:
> If I try to sign and encrypt in the same command line I end up with
> complaints about unable to decrypt PKCS7 structure.
Okay, so that means S/MIME should default to doing two separate
commands for sign+encrypt. Perhaps tonight I'll dig into the mml2015
stuff to figure out what controls a sign+encrypt. Of course, this
being Gnus, we should make this ridiculously configurable! ;)
> It works great. Thanks!
Excellent.
--
Josh Huber
prev parent reply other threads:[~2002-04-16 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 19:47 David S. Goldberg
2002-04-14 3:49 ` Josh Huber
2002-04-16 18:28 ` David S. Goldberg
2002-04-16 22:25 ` Josh Huber [this message]
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=87sn5v8enu.fsf@alum.wpi.edu \
--to=huber@alum.wpi.edu \
/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).