1996-01-03 - crypto (semi-)export issue

Header Data

From: m5@dev.tivoli.com (Mike McNally)
To: cypherpunks@toad.com
Message Hash: 3b5802cc78e14aba07ff7a61ac07a7ecf1b6029742df85ebc9c8e9eebeac3253
Message ID: <9601032309.AA16448@alpha>
Reply To: N/A
UTC Datetime: 1996-01-03 23:48:55 UTC
Raw Date: Thu, 4 Jan 1996 07:48:55 +0800

Raw message

From: m5@dev.tivoli.com (Mike McNally)
Date: Thu, 4 Jan 1996 07:48:55 +0800
To: cypherpunks@toad.com
Subject: crypto (semi-)export issue
Message-ID: <9601032309.AA16448@alpha>
MIME-Version: 1.0
Content-Type: text/plain



It's been a while since this went 'round, and my memories are hazy of
the details.

Isn't it the case that there are loopholes or explicit exceptions in
crypto export regulations that allow American businesses to supply
their overseas operatives with tools for secure communication back
home?  We were discussing today some stuff about our web server, and
there's some desire to provide secure access for our sales people to
internal junk.  Nobody was sure whether it'd be OK for our people in
the Evil Empire (Europe) to have the 128-bit-RC4 Netscape for that
purpose.

(If so, I wonder if the exceptions apply to other munitions too?
Like, maybe it's OK to take a medium-range missile overseas if you're
just going to use it to blow up your manager's office :-)

(No, I don't hate my manager.)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Nobody's going to listen to you if you just | Mike McNally (m5@tivoli.com) |
| stand there and flap your arms like a fish. | Tivoli Systems, Austin TX    |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





Thread