Re: Comments on x942-05 draft

Russ Housley <housley@spyrus.com> Thu, 04 March 1999 20:55 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 PAA12533 for <smime-archive@odin.ietf.org>; Thu, 4 Mar 1999 15:55:48 -0500 (EST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id LAA17260 for ietf-smime-bks; Thu, 4 Mar 1999 11:48:45 -0800 (PST)
Received: from thehub.knight-hub.com (root@thehub.knight-hub.com [205.177.16.3]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id LAA17256 for <ietf-smime@imc.org>; Thu, 4 Mar 1999 11:48:44 -0800 (PST)
Received: from rhousley_laptop.spyrus.com ([205.177.169.194]) by thehub.knight-hub.com (8.8.8/8.8.8) with SMTP id OAA21872; Thu, 4 Mar 1999 14:54:12 -0500
Message-Id: <4.1.19990304124721.00985440@209.172.119.123>
Message-Id: <4.1.19990304124721.00985440@209.172.119.123>
X-Sender: rhousley#207.212.34.30@209.172.119.123 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Thu, 04 Mar 1999 12:57:26 -0500
To: Eric Rescorla <ekr@rtfm.com>
From: Russ Housley <housley@spyrus.com>
Subject: Re: Comments on x942-05 draft
Cc: jlinn@securitydynamics.com, ietf-smime@imc.org, burt@RSA.COM
In-Reply-To: <199902221714.JAA26885@speedy.rtfm.com>
References: <Your message of "Fri, 19 Feb 1999 08:50:30 EST." <D104150098E6D111B7830000F8D90AE845A4B4@exna02.securitydynamics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

Eric:

I am comfortable mandating the effective and real key lengths are the same
for the calculation of the key-encrypting key.  If some policy wants to use
a reduced effective key length for the content-encryption key, thsi can
still be accomodated.

Russ


At 09:14 AM 2/22/99 -0800, Eric Rescorla wrote:
>> Here's some analysis on the RC2 effective key issue, thanks to Burt Kaliski.
>[...]
>Clearly we do have to defend against the partition attack on effective
>key lengths. 
>
>As John suggests, I propose that we place the RC2 effective key 
>length into the the suppPubInfo. However, this leaves us with
>an unfortunate inconsistency, in that for some algorithms it's
>the length and some it's the effective length. One solution
>to this would be to revert to what Stephen Henson has termed
>the X/8 strategy. I.e. make the effective and real lengths
>the same for RC2. This is slightly more tasteful than having
>a bunch of special case language.
>
>Comments? I'd like to get this settled quickly.
>
>-Ekr
>[Eric Rescorla                                   ekr@rtfm.com]
>