1995-08-24 - BruteSSL: WTF? 0c2b-cf7a NOACK 0c2b 50000 Joe Thomas jthomas@ogi.com

Header Data

From: jered@MIT.EDU
To: cypherpunks@toad.com
Message Hash: 468264f24bf1e66e6f040c0548a315fa3b8e52c4fb0a779ced839b46d7a5b2a4
Message ID: <199508242031.QAA04083@narn.atype.com>
Reply To: N/A
UTC Datetime: 1995-08-24 20:32:08 UTC
Raw Date: Thu, 24 Aug 95 13:32:08 PDT

Raw message

From: jered@MIT.EDU
Date: Thu, 24 Aug 95 13:32:08 PDT
To: cypherpunks@toad.com
Subject: BruteSSL: WTF? 0c2b-cf7a NOACK 0c2b 50000 Joe Thomas <jthomas@ogi.com>
Message-ID: <199508242031.QAA04083@narn.atype.com>
MIME-Version: 1.0
Content-Type: text/plain



It appears that Joe Thomas <jthomas@ogi.com> has more or less locked
(until things start getting reassigned) most of the keyspace.  Even if
he had a MasPar, it would still take him more than 2 days to check this
space.  Does anyone know what the deal with this is?  A simple error?
A malicious attack? (I think that the SKSP is far to insecure to be
effective....I could falsely ACK parts of the keyspace if I wanted to be
mean.) An NSA agent who will check that keyspace and return the results
in the next hour?

--Jered
jered@mit.edu





Thread