1995-09-03 - Re: A bold ssl idea ?

Header Data

From: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
To: lyalc@ozemail.com.au (lyal collins)
Message Hash: 334aa572ad706cace5fcafc030bf1c91dfcb6740596162368b1c76529458ba2f
Message ID: <“swan.cl.cam.:180200:950903143250”@cl.cam.ac.uk>
Reply To: <199509031145.VAA12843@oznet02.ozemail.com.au>
UTC Datetime: 1995-09-03 15:25:01 UTC
Raw Date: Sun, 3 Sep 95 08:25:01 PDT

Raw message

From: Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
Date: Sun, 3 Sep 95 08:25:01 PDT
To: lyalc@ozemail.com.au (lyal collins)
Subject: Re: A bold ssl idea ?
In-Reply-To: <199509031145.VAA12843@oznet02.ozemail.com.au>
Message-ID: <"swan.cl.cam.:180200:950903143250"@cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain


> I understand that setting up RC4 keys is slower that testing for the correct
> key (I may have misuderstood this bit).

For pure RC4, Yes.  However, SSL is not pure RC4.

> Is it considered practical to modify the brutessl code to have multiple
> message data, and test each against a key from allocated key space ?

You are the third person I've heard think of this.
[ The first did quite a lot of calculations before spotting the problem ! ]

> If so, this may mean that perhaps 3 message can be tested against a single
> in the time two single keys could be tested against one message.

Well, the original suggestion I heard was to try 64K at a time :-))





Thread