RE: Issues with S/MIME Message Specification
William Whyte <wwhyte@baltimore.ie> Tue, 18 May 1999 20:28 UTC
Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15502 for <smime-archive@odin.ietf.org>; Tue, 18 May 1999 16:28:15 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id MAA18918 for ietf-smime-bks; Tue, 18 May 1999 12:35:29 -0700 (PDT)
Received: from puma.baltimore.ie (firewall-user@pc215-8.indigo.ie [194.125.215.8]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id MAA18914 for <ietf-smime@imc.org>; Tue, 18 May 1999 12:35:27 -0700 (PDT)
Received: by puma.baltimore.ie; id VAA20768; Tue, 18 May 1999 21:08:38 +0100 (GMT/IST)
Received: from ocelot.baltimore.ie(10.49.0.10) by puma.baltimore.ie via smap (4.1) id xma020753; Tue, 18 May 99 21:07:39 +0100
Received: from knuckle (knuckle.baltimore.ie [10.49.0.103]) by ocelot.baltimore.ie (8.8.7/8.8.5) with SMTP id UAA07751; Tue, 18 May 1999 20:34:29 +0100
Received: by localhost with Microsoft MAPI; Tue, 18 May 1999 20:33:58 +0100
Message-ID: <01BEA16D.C1807100.wwhyte@baltimore.ie>
From: William Whyte <wwhyte@baltimore.ie>
To: "'pgut001@cs.aucKland.ac.nz'" <pgut001@cs.aucKland.ac.nz>, "bjueneman@novell.com" <bjueneman@novell.com>, "ietf-smime@imc.org" <ietf-smime@imc.org>
Subject: RE: Issues with S/MIME Message Specification
Date: Tue, 18 May 1999 20:33:57 +0100
Organization: Baltimore Technologies
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit
> >Finally, somewhere in these documents there is a statement regarding the > >advisability of including the content encryption key encrypted in the > >originator's public key, but despite rereading the documents multiple > >times I can't find that text again. As I recall, the text said that this > >SHOULD be done.... > > Given that anyone who wants to re-read their own messages will keep a copy > stored locally, why on earth would they go through the complex encrypt-> > decrypt process just to read what they've written? I think even the presence > of SHOULD is too restrictire for this, > ... > Anyone who > needs sent-mail revocation and whatnot desperately enough can go use X.400 > for their mail. Not quite right. If you're using (for example) Outlook, the message that's stored in your Sent Mail box is the message that was actually sent. You need to have encrypted it to yourself to be able to read it subsequently. William
- Re: Issues with S/MIME Message Specification Peter Gutmann
- RE: Issues with S/MIME Message Specification William Whyte
- Re: Issues with S/MIME Message Specification Peter Gutmann
- RE: Issues with S/MIME Message Specification Jim Schaad (Exchange)
- RE: Issues with S/MIME Message Specification Bob Jueneman
- Re: Issues with S/MIME Message Specification Bob Jueneman
- RE: Issues with S/MIME Message Specification Andrew Ferguson
- Re: Issues with S/MIME Message Specification Enzo Michelangeli
- RE: Re: Issues with S/MIME Message Specification bartley.o'malley
- RE: Issues with S/MIME Message Specification Peter Gutmann
- Export Restrictions (was Re: Issues with S/MIME M… C. Harald Koch
- RE: Issues with S/MIME Message Specification Paul Hoffman / IMC
- Re: Issues with S/MIME Message Specification Russ Housley
- Re: Issues with S/MIME Message Specification Russ Housley