[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSA denies our 3DES license

To: ipsec@ans.net
Subject: Re: NSA denies our 3DES license
From: Derrell Piper <piper@tgv.com>
Date: Tue, 19 Mar 96 07:39:08 -0800
In-Reply-To: Your message of "Tue, 19 Mar 96 09:01:02 EST." <2.2.32.19960319140102.00e1e19c@pop3hub.is.chrysler.com>
Sender: ipsec-request@neptune.tis.com

>Can RC5 parameters be set so that it reaches 3DES strength, and if so, if
>the keying protocol allows for full parameter control, might NSA do the same
>with RC5 as it is doing to 3DES?  Or specify that the keying protocol lock
>down a certain set of RC5 parameters?

RC5 is a stream cipher that allows for variable length keys.  I would guess
that RC5 using 40-bit (or less) keys would be exportable, but greater than
40 bits would not.  That's what's been done for other ciphers that employ
variable length keys.

Derrell Piper   | piper@tgv.com      | 408/457-5384
TGV, Inc.       | 101 Cooper Street  | Santa Cruz, CA 95060 USA

Follow-Ups:

Re: NSA denies our 3DES license

From: "Perry E. Metzger" <perry@piermont.com>

Re: NSA denies our 3DES license

From: "Angelos D. Keromytis" <kermit@forthnet.gr>

References:

Re: NSA denies our 3DES license

From: Robert Moskowitz <rgm3@is.chrysler.com>

Prev by Date: Re: ESP transform with RC5
Next by Date: Re: ESP transform with RC5
Prev by thread: Re: NSA denies our 3DES license
Next by thread: Re: NSA denies our 3DES license
Index(es):
- Main
- Thread