IETF Logo Mail Archive

Re: secure sign & encrypt

pgut001@cs.auckland.ac.nz (Peter Gutmann) Fri, 24 May 2002 05:05 UTC

Received: from above.proper.com (mail.imc.org [208.184.76.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08425 for <openpgp-archive@odin.ietf.org>; Fri, 24 May 2002 01:05:51 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id g4O4w7H23848 for ietf-openpgp-bks; Thu, 23 May 2002 21:58:07 -0700 (PDT)
Received: from mailhost2.auckland.ac.nz (mailhost2.auckland.ac.nz [130.216.1.4]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4O4w6L23844 for <ietf-openpgp@imc.org>; Thu, 23 May 2002 21:58:06 -0700 (PDT)
Received: from mailhost-mp.auckland.ac.nz (IDENT:mirapoint@mailhost-mp.auckland.ac.nz [130.216.191.61]) by mailhost2.auckland.ac.nz (8.9.2/8.9.2/8.9.2-ua) with ESMTP id QAA01170; Fri, 24 May 2002 16:58:09 +1200 (NZST)
Received: from hermes.cs.auckland.ac.nz (hermes.cs.auckland.ac.nz [130.216.35.151]) by mailhost-mp.auckland.ac.nz (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id ADO38172; Fri, 24 May 2002 16:58:08 +1200 (NZST)
Received: from ruru.cs.auckland.ac.nz (ruru-nfs.cs.auckland.ac.nz [130.216.35.12]) by hermes.cs.auckland.ac.nz (8.12.3/8.12.3) with ESMTP id g4O4w8AC008809; Fri, 24 May 2002 16:58:08 +1200
Received: (from pgut001@localhost) by ruru.cs.auckland.ac.nz (8.9.3/8.8.6/cs-slave) id QAA43063; Fri, 24 May 2002 16:58:06 +1200 (NZST) (sender pgut001@cs.auckland.ac.nz)
Date: Fri, 24 May 2002 16:58:06 +1200
Message-ID: <200205240458.QAA43063@ruru.cs.auckland.ac.nz>
From: pgut001@cs.auckland.ac.nz
To: Terje.Braaten@concept.fr, dpkemp@missi.ncsc.mil
Subject: Re: secure sign & encrypt
Cc: ietf-openpgp@imc.org
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>

"David P. Kemp" <dpkemp@missi.ncsc.mil> writes:

>Each layer does what it does - if you want the security services provided by
>three layers (ESE), or what S/MIME calls triple-wrapping (SES), then you must
>use three layers.

The motivation for S/MIME triple wrap was AFAIK use by automated mail gateways.
If you always have to sign the plaintext then it makes it impossible to create
a mail gateway which only lets signed data in or out, because the gateway would
have to hold all the private keys in order to verify the sigs.  Thus the SES
triple-wrap.  I know Don Davis looked at the RFC which covered this (2633?)
when he was writing his paper and found it didn't really solve the problem.

Peter.

v2.23.0 | Report a Bug | By Email