1995-08-24 - Brute SSL Challenge
Header Data
From: David Neal <dneal@usis.com>
To: cypherpunks@toad.com
Message Hash: da8cd3d05532c541073298186b0130f06b384c26756aba2e8e9fde5379d26b4d
Message ID: <199508240552.AAA00601@gnupln8.usis.com>
Reply To: N/A
UTC Datetime: 1995-08-24 05:54:02 UTC
Raw Date: Wed, 23 Aug 95 22:54:02 PDT
Raw message
From: David Neal <dneal@usis.com>
Date: Wed, 23 Aug 95 22:54:02 PDT
To: cypherpunks@toad.com
Subject: Brute SSL Challenge
Message-ID: <199508240552.AAA00601@gnupln8.usis.com>
MIME-Version: 1.0
Content-Type: text/plain
Just skip this silly little message if you know enough to
optimize the brutessl code.
Didn't know of a better place to put this, so please no flames.
Hopefully everyone on here is accomplished enough to know
optimizing the brutessl code helps immensely. If not, well I used
gcc -O6 -funroll-loops -fomit-frame-pointer -finline-functions -c search.c
gcc -O6 -funroll-loops -fomit-frame-pointer -finline-functions -o brutessl \
brutessl.c search.o
To go from 5,000 keys per second to 10,100 keys per second.
Thread
Return to August 1995
- Return to “David Neal <dneal@usis.com>”
- Return to “Piete Brooks <Piete.Brooks@cl.cam.ac.uk>”
Return to “zinc <zinc@zifi.genetics.utah.edu>”
- 1995-08-24 (Wed, 23 Aug 95 22:54:02 PDT) - Brute SSL Challenge - David Neal <dneal@usis.com>
- 1995-08-24 (Thu, 24 Aug 95 00:06:01 PDT) - Re: Brute SSL Challenge - Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
- 1995-08-24 (Thu, 24 Aug 95 01:13:09 PDT) - Re: Brute SSL Challenge - zinc <zinc@zifi.genetics.utah.edu>
- 1995-08-24 (Thu, 24 Aug 95 00:06:01 PDT) - Re: Brute SSL Challenge - Piete Brooks <Piete.Brooks@cl.cam.ac.uk>