From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: signing and encrypting with new <#secure> tag
Date: Fri, 12 Apr 2002 15:47:34 -0400 [thread overview]
Message-ID: <m1bu1qgn1gp.fsf@blackbird.mitre.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Using smime, it appears that I am unable to both encrypt and sign a
message. If I try to force two <#secure ...> tags, or put two modes
into a single one, I only get whatever is placed first. Right now I
have a workaround, Running both mml-secure-sign-smime and
mml-secure-encrypt-smime generates a
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
tag that handles both
signing and encrypting, but those commands are obviously deprecated.
--
Dave Goldberg
david.goldberg6@verizon.net
next reply other threads:[~2002-04-12 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 19:47 David S. Goldberg [this message]
2002-04-14 3:49 ` Josh Huber
2002-04-16 18:28 ` David S. Goldberg
2002-04-16 22:25 ` Josh Huber
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=m1bu1qgn1gp.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.net \
/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).