1996-08-01 - Re: Cracking RC4/40 for massive wiretapps

Header Data

From: Hal <hfinney@shell.portal.com>
To: cypherpunks@toad.com
Message Hash: 5e2a3d57d05de0e3a6518e010ddc62746c4e265f074666dd0053b4be610b5d96
Message ID: <199608011709.KAA17457@jobe.shell.portal.com>
Reply To: <199608011151.HAA07754@unix.asb.com>
UTC Datetime: 1996-08-01 21:17:20 UTC
Raw Date: Fri, 2 Aug 1996 05:17:20 +0800

Raw message

From: Hal <hfinney@shell.portal.com>
Date: Fri, 2 Aug 1996 05:17:20 +0800
To: cypherpunks@toad.com
Subject: Re: Cracking RC4/40 for massive wiretapps
In-Reply-To: <199608011151.HAA07754@unix.asb.com>
Message-ID: <199608011709.KAA17457@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain


When I wrote my previous message about the use of lookup tables, I forgot
about the use of salt, extra key bits which vary per message and are sent
in the clear.  That defeats the table lookup approach for searching for
messages which were encrypted with a given key.  There are really 128 key
bits per message, with 40 of them kept secret.

Hal

Thread

• Return to August 1996

• Return to ““Deranged Mutant” <WlkngOwl@unix.asb.com>”

• Return to “Hal <hfinney@shell.portal.com>”

• 1996-08-01 (Thu, 1 Aug 1996 22:34:17 +0800) - Re: Cracking RC4/40 for massive wiretapps - “Deranged Mutant” <WlkngOwl@unix.asb.com>
  • 1996-08-01 (Fri, 2 Aug 1996 02:34:02 +0800) - Re: Cracking RC4/40 for massive wiretapps - Hal <hfinney@shell.portal.com>
  • 1996-08-01 (Fri, 2 Aug 1996 05:17:20 +0800) - Re: Cracking RC4/40 for massive wiretapps - Hal <hfinney@shell.portal.com>