RE: digested-data, surreptitious forwarding, D-H

Trevor Perrin <Tperrin@sigaba.com> Sat, 27 July 2002 02:42 UTC

Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15978 for <smime-archive@lists.ietf.org>; Fri, 26 Jul 2002 22:42:50 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g6R2SiV29523 for ietf-smime-bks; Fri, 26 Jul 2002 19:28:44 -0700 (PDT)
Received: from bsd.sigaba.com (bsd.sigaba.com [67.113.238.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6R2Sew29519 for <ietf-smime@imc.org>; Fri, 26 Jul 2002 19:28:41 -0700 (PDT)
Received: from exchange1.sigaba.com (exchange1.sigaba.com [10.10.10.10]) by bsd.sigaba.com (8.12.2/8.12.2) with ESMTP id g6R2Sc3E009758 for <ietf-smime@imc.org>; Fri, 26 Jul 2002 19:28:38 -0700
Received: by exchange.sigaba.com with Internet Mail Service (5.5.2653.19) id <PVNJC1L3>; Fri, 26 Jul 2002 19:28:33 -0700
Message-ID: <2129B7848043D411881A00B0D0627EFEBFB086@exchange.sigaba.com>
From: Trevor Perrin <Tperrin@sigaba.com>
To: Trevor Perrin <Tperrin@sigaba.com>, "'ietf-smime@imc.org'" <ietf-smime@imc.org>
Subject: RE: digested-data, surreptitious forwarding, D-H
Date: Fri, 26 Jul 2002 19:28:32 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>



scratch question 3, this week has fried my brains more than I thought..

> -----Original Message-----
> From: Trevor Perrin [mailto:Tperrin@sigaba.com]
> Sent: Friday, July 26, 2002 2:32 PM
> To: 'ietf-smime@imc.org'
> Subject: digested-data, surreptitious forwarding, D-H
> 
> 
> 
> 
> With more diligence I probably could've answered these from 
> the archives.
> But a few questions:
> 
> 1) I'm surprised S/MIME doesn't use CMSs' digested-data with 
> enveloped-data.
> In the case of encrypted but not signed mails, doesn't this leave the
> message vulnerable to things like cut-and-paste attacks 
> (where an attacker
> reorders ciphertext blocks, so upon decrypting the recipient 
> sees reordered
> plaintext)?
> 
> 2) At some point I thought there was an Internet-Draft for a signed
> attribute to address Don Davis' surreptitious forwarding 
> concern.  I don't
> see it now.  Has that been dropped, or has some other fix 
> been incorporated
> somewhere?
> 
> 3) I see that Diffie-Hellman key pairs can be encrypted to, 
> using either
> static-static or ephemeral-static modes.  It seems like a 
> Diffie-Hellman key
> pair should be able to sign as well, using something like a 
> static-ephemeral
> mode.  Is there a cryptographic reason why this 
> can't/shouldn't be done, or
> is it just incidental that it isn't supported?  
> 
> The reason it seems like this might be useful is that Diffie-Hellman
> agreement values can be cached, so a signer could perform 
> lots of signatures
> efficiently with such a key pair, which could be useful for 
> something like a
> DOMSEC gateway, which may have high volume mail flows and 
> large key pairs.
> 
> Trevor
>