1996-06-04 - Re: NRC Session Hiss

Header Data

From: shamrock@netcom.com (Lucky Green)
To: Raph Levien <raph@cs.berkeley.edu>
Message Hash: 0f637f10d9f20d70d5858a5728550c46f40d750e084d4b6306e0a55f4612da13
Message ID: <v02120d0badd919d1ddb3@[192.0.2.1]>
Reply To: N/A
UTC Datetime: 1996-06-04 03:35:42 UTC
Raw Date: Tue, 4 Jun 1996 11:35:42 +0800

Raw message

From: shamrock@netcom.com (Lucky Green)
Date: Tue, 4 Jun 1996 11:35:42 +0800
To: Raph Levien <raph@cs.berkeley.edu>
Subject: Re: NRC Session Hiss
Message-ID: <v02120d0badd919d1ddb3@[192.0.2.1]>
MIME-Version: 1.0
Content-Type: text/plain


At 15:58 6/3/96, Raph Levien wrote:

>   Basically, an exportable S/MIME client can transmit messages up to
>1024/40 bit RSA/RC2 (or RSA/DES), and receive messages up to 512/64 bit
>RSA/RC2 (or RSA/DES, but in the latter case I would imagine it's actually
>restricted to 512/56 because of the keysize of DES). Note that the
>asymmetry actually points in different directions for the public and
>symmetric keysizes.

What will be the maximum keysize for a domestic encryption client? It it is
larger than 1024 bits, there will be interoperability problems with foreign
clients. If the domestic client is limited to 1024 bits, it would set a bad
precedence, since it would effectively require that the encryption key is
smaller than the largest signature key.


Disclaimer: My opinions are my own, not those of my employer.

-- Lucky Green <mailto:shamrock@netcom.com>
   PGP encrypted mail preferred.







Thread