Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: decrypting S/MIME messages
Date: Sat, 28 Jul 2001 04:29:58 +0200	[thread overview]
Message-ID: <iluy9p9ss49.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <ey3d7igwy6.fsf@vsu.ru> (Vladimir Volovich's message of "Fri, 27 Jul 2001 20:26:25 +0400")

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?

You're right, the framework is there but the glue is missing.

There was a minor problem adding the glue, application/pkcs7-mime is a
catch-all MIME tag and it can be almost any PKCS#7 blob.  To find out
what kind of operation should be performed (decryption, verification,
or simple unwrapping) one need to look inside the PKCS#7 blob.  I
wrote a ASN.1 parser in elisp and had everything almost working some
moons ago, but lost it in a harddisk crash.  The ASN.1 parser isn't
really necessary, a carefully constructed `looking-at' invocation is
sufficient, and unless I get very bored I won't write another ASN.1
parser so the `looking-at' approach is probably the way to go.  I've
almost finished this, and I'll try to get some time to commit it this
tomorrow.



  reply	other threads:[~2001-07-28  2:29 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 [this message]
2001-07-29  1:13   ` Simon Josefsson
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=iluy9p9ss49.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).