1995-08-24 - Re: Subject: ANNOUNCE: 2nd SSL challenge - we need your compute!

Header Data

From: aba@dcs.exeter.ac.uk
To: somogyi@digmedia.com (Stephan Somogyi)
Message Hash: a29f86f99413d0dc2b67846e3428c8c38408eea0fb204b4e053cfd012aedfbec
Message ID: <9231.9508240754@exe.dcs.exeter.ac.uk>
Reply To: N/A
UTC Datetime: 1995-08-24 07:55:28 UTC
Raw Date: Thu, 24 Aug 95 00:55:28 PDT

Raw message

From: aba@dcs.exeter.ac.uk
Date: Thu, 24 Aug 95 00:55:28 PDT
To: somogyi@digmedia.com (Stephan Somogyi)
Subject: Re: Subject: ANNOUNCE: 2nd SSL challenge - we need your compute!
Message-ID: <9231.9508240754@exe.dcs.exeter.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain



> I have a working version of BruteSSL 1.02 (without SKSP client) for
> Power Macintosh. However, as I don't want to run the risk of
> violating ITAR, I'm still investigating ways of making it
> available. Suggestions are welcome.

Just send it along... several people have been shipping various DOS
binaries out of the US, with out the source.

The presumption taken was that as long as they didn't ship search.c or
assembly.c, there is no crypto source, and the binary could not be
used to encrypt anything.  (Also it's for SSL with 40 bit keys which
is export approved anyway).

You can ship a diff for brutessl.c (which contains no crypto code) if
you want the mods to be mixed back in (please include some kind of
#ifdef __MAC or whatever the standard _i_am_a_mac macro is).  Or if
that makes you uncomfortable, well we'll do with out the source.

Reckon you'd be safe enough.

Anyone think otherwise?

Adam






Thread