From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: decrypting S/MIME messages
Date: Sun, 29 Jul 2001 03:13:23 +0200 [thread overview]
Message-ID: <ilun15ozgek.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <iluy9p9ss49.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 28 Jul 2001 04:29:58 +0200")
Vladimir Volovich <vvv@vsu.ru> writes:
> The question is: how should i view encrypted s/mime messages? why
> there are no calls to smime-decrypt-buffer done by gnus automatically?
>
> Is it just not-yet-implemented, but all framework is there already?
Ok, S/MIME decryption work for me now, tell me if it work for you.
S/MIME signatures using opaque PKCS#7 blobs isn't implemented, if
someone encounter these I'd prefer a bug report to find out what
mailer creates such beasts. (Adding support for them in Gnus is a
five-liner.)
next prev parent reply other threads:[~2001-07-29 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 16:26 Vladimir Volovich
2001-07-28 2:29 ` Simon Josefsson
2001-07-29 1:13 ` Simon Josefsson [this message]
2001-07-29 13:00 ` Vladimir Volovich
2001-07-29 14:44 ` Amos Gouaux
2001-07-29 20:14 ` Simon Josefsson
2001-07-30 9:39 ` Vladimir Volovich
2001-07-30 22:26 ` Simon Josefsson
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=ilun15ozgek.fsf@barbar.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).