From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37540 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: MML multipart tag -- what does it do? Date: Sun, 05 Aug 2001 21:54:56 +0200 Message-ID: References: <2nr8utf2u6.fsf@piglet.jia.vnet> <874rrolurg.fsf@smarttrust.com> <87zo9fq1az.fsf@deneb.enyo.de> <87ofpu330w.fsf@deneb.enyo.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172937 14418 80.91.224.250 (21 Oct 2002 04:02:17 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:02:17 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 4826 invoked from network); 5 Aug 2001 19:54:05 -0000 Original-Received: from dolk.extundo.com (195.42.214.242) by gnus.org with SMTP; 5 Aug 2001 19:54:05 -0000 Original-Received: from barbar.josefsson.org (slipsten.extundo.com [195.42.214.241]) (authenticated) by dolk.extundo.com (8.11.3/8.11.3) with ESMTP id f75JsBw16315; Sun, 5 Aug 2001 21:54:12 +0200 Original-To: Florian Weimer In-Reply-To: <87ofpu330w.fsf@deneb.enyo.de> (Florian Weimer's message of "Sun, 05 Aug 2001 18:06:07 +0200") Mail-Copies-To: nobody User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104 Original-Lines: 31 Xref: main.gmane.org gmane.emacs.gnus.general:37540 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37540 Florian Weimer writes: > Simon Josefsson writes: > >> This requires users to know how the sign/encrypt mechanism they use >> are implemented in MIME. E.g., if you want to sign using PGP/MIME you >> must write the above, if you want to encrypt with S/MIME you need to >> write something completely different because S/MIME encryption doesn't >> use RFC 1847. > > Really? I assumed it did, and using S/MIME in a RFC 1847 context is > indeed described in the S/MIME RFCs... Not for encryption. The application/pkcs7-mime type may also contain signed data as well, so you don't need RFC 1847 to use S/MIME fully. (a/pkcs7-mime basicly just contains a PKCS#7 blob, which might contain lots of stuff.) I've no idea why. I think it would've been trivial to take the same approach as RFC 2015 did (the first part just being some dummy "Version: 1" and the second everything that is in the current application/pkcs7-mime part). It's interesting to note that searching the IETF S/MIME mailing list 1996-2001 for multipart/encrypted gives one match, and it's irrelevant. Hmm. Also, the "mime" in "sign=pgpmime" was deliberately chosen, so that you could support "sign=pgp" (plain PGP) via MML at some point, and the current approach would work nicely with that. Then we would be able to send mail to people with Outlook with crippled PGP plugins (which seem to be a quite large population).