From: monty.harder@famend.com (MONTY HARDER)
To: CYPHERPUNKS@toad.com
Message Hash: e1ce78ae1071346397d0ae8edbafe86eb78e68f2f88767300f98b726077b88fa
Message ID: <8AFE51A.0003000395.uuout@famend.com>
Reply To: N/A
UTC Datetime: 1995-08-27 04:26:15 UTC
Raw Date: Sat, 26 Aug 95 21:26:15 PDT
From: monty.harder@famend.com (MONTY HARDER)
Date: Sat, 26 Aug 95 21:26:15 PDT
To: CYPHERPUNKS@toad.com
Subject: SSL trouble
Message-ID: <8AFE51A.0003000395.uuout@famend.com>
MIME-Version: 1.0
Content-Type: text/plain
DD> In conclusion, I think random searching is the way to go. It's even better
DD> than Monty's pre-allocation with quad-coverage.
Here's a thought: How about the best of both worlds. Keep the
double-coverage, bidirectional sweep, and allocate only one "team". The
client software will take the pre-allocated segment, and then go random
for the rest of the run.
* GHOTI = FISH?
touGH: GH = F
wOmen: O = I
dicTIonary: TI=SH.
I love English!
---
* Monster@FAmend.Com *
Return to August 1995
Return to “monty.harder@famend.com (MONTY HARDER)”
1995-08-27 (Sat, 26 Aug 95 21:26:15 PDT) - SSL trouble - monty.harder@famend.com (MONTY HARDER)