Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: signing and encrypting with new <#secure> tag
Date: Sat, 13 Apr 2002 23:49:25 -0400	[thread overview]
Message-ID: <874rif2b3u.fsf@alum.wpi.edu> (raw)
In-Reply-To: <m1bu1qgn1gp.fsf@blackbird.mitre.org>

david.goldberg6@verizon.net (David S. Goldberg) writes:

> 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 tag that handles both signing
> and encrypting, but those commands are obviously deprecated.

Well, they're not deprecated really, but they don't do the Right Thing
when your message has multiple parts.  Those functions are for signing
& encrypting parts of a message, and the <#secure tags are basically a
meta tag which expands to either a part or multipart tag depending on
if there are attachments in the message.

Now, as for encrypt & sign, what to do?

I don't use S/MIME, so I didn't get a chance to test the secure tags
for it.

With PGP/MIME right now encrypting signs as well...

There are basically 2 ways to do it with PGP/MIME:

1) sign the message using standard PGP/MIME signing, then encrypt that
   message.
2) encrypt the message with an embedded signature (using --sign with
   GnuPG)

I like method 2, since it happens with one pass of gpg, and is less
computatationally intensive. (and seems cleaner as well!)

Right now if you do <!part sign=pgpmime encrypt=pgpmime> it does
method #1...well, actually it signs the message, then encrypts it with
the embedded signature. (since the gpg encrypt functions automatically
use --sign when encrypting)

How does S/MIME handle sign+encrypt?

Just curious, since I'd like to change the default to
mode=signencrypt, but have the ability to use encrypt only as well.

I'm about to commit a fix which does change this.  Look at
lisp/mml-sec.el (at the bottom) for more information.

Basically, the pgp and pgpmime functions use mode=encrypt for now
(always), but the smime ones default to signencrypt.  I've set it up
so if you give the encrypt option a prefix argument it goes back to
only encrypting.

Please try it out!

PS:
on a side note, is there anything equivalent to ,@ for use outside of
backquote? I often find that it would be useful to flatten a list in
place without surrounding the outside form with `.

-- 
Josh Huber



  reply	other threads:[~2002-04-14  3:49 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 [this message]
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=874rif2b3u.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).