1995-11-14 - Re: NSA, ITAR, NCSA and plug-in hooks.

Header Data

From: Simon Spero <ses@tipper.oit.unc.edu>
To: Rich Salz <rsalz@osf.org>
Message Hash: dda8686a9e5879955792f95f147251ad0980e4c7d6be9b3cc4462cfbbf722f60
Message ID: <Pine.SOL.3.91.951114115921.17855A-100000@chivalry>
Reply To: <9511141920.AA13573@sulphur.osf.org>
UTC Datetime: 1995-11-14 20:26:30 UTC
Raw Date: Wed, 15 Nov 1995 04:26:30 +0800

Raw message

From: Simon Spero <ses@tipper.oit.unc.edu>
Date: Wed, 15 Nov 1995 04:26:30 +0800
To: Rich Salz <rsalz@osf.org>
Subject: Re: NSA, ITAR, NCSA and plug-in hooks.
In-Reply-To: <9511141920.AA13573@sulphur.osf.org>
Message-ID: <Pine.SOL.3.91.951114115921.17855A-100000@chivalry>
MIME-Version: 1.0
Content-Type: text/plain


On Tue, 14 Nov 1995, Rich Salz wrote:

> As I said in my original message about Pegasus:
> 	The NSA consider this kind of thing "crypto with a hole"
> 	It's stupid, the hole is the crypto.  But, the rest of
> 	the code is considered by the Agency to be an "ancilliary
> 	device" as defined under ITAR.

The interesting question is how narrow the interface has to be before it 
becomes in violation of the ITAR. Is the key question whether the "holes" 
are specifically designed for the insertion of cryptographic materials, 
or is it the fact that they could be used to support cryptographic 
enhancements?






Thread