cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1998-01-06 - Silly Shrinkwrapped Encryption

Header Data

From: Eric Cordian <emc@wire.insync.net>
To: cypherpunks@cyberpass.net
Message Hash: d8c5dacf329bf34b7744fb608d690318e3d87a1fac35029663347f4f18e4328a
Message ID: <199801061930.NAA09848@wire.insync.net>
Reply To: N/A
UTC Datetime: 1998-01-06 19:35:58 UTC
Raw Date: Wed, 7 Jan 1998 03:35:58 +0800

Raw message

From: Eric Cordian <emc@wire.insync.net>
Date: Wed, 7 Jan 1998 03:35:58 +0800
To: cypherpunks@cyberpass.net
Subject: Silly Shrinkwrapped Encryption
Message-ID: <199801061930.NAA09848@wire.insync.net>
MIME-Version: 1.0
Content-Type: text/plain



Could someone poke through Lotus Notes with a debugger and see exactly how
this "giving 24 bits to the government" is implemented? 

Most commercial software simply introduces redundancy in order to limit
the keyspace to 40 bits, regardless of the advertised length of the key. 
This claim that they deliver 64 bits of key to the customer seems a bit
bogus. 

Of course, they could have done something clever, like generating a
completely random 64 bit key, and then encrypting 24 bits of it with a
giant government-owned RSA public key, and including this additional
information with each message.  However, it seems unlikely that they would
employ such strong encryption for message recovery, while offering only 64
bits for message encryption. 

Is Lotus Notes encryption documented anywhere?  Are the differences
between the export and domestic versions disclosed to overseas customers?

--
Eric Michael Cordian 0+
O:.T:.O:. Mathematical Munitions Division
"Do What Thou Wilt Shall Be The Whole Of The Law"

Thread