cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1996-04-14 - Re: Is crypt(1) a prohibited export?

Header Data

From: Dan Busarow <dan@dpcsys.com>
To: Jeremey Barrett <jeremey@forequest.com>
Message Hash: 88caff98d0840e22027aace69a5aba3f4620671a22c64e3189bb619b60ea811a
Message ID: <Pine.SV4.3.91.960414010416.20213C-100000@cedb>
Reply To: <Pine.BSI.3.91.960413221855.7580A-100000@newton.forequest.com>
UTC Datetime: 1996-04-14 12:16:42 UTC
Raw Date: Sun, 14 Apr 1996 20:16:42 +0800

Raw message

From: Dan Busarow <dan@dpcsys.com>
Date: Sun, 14 Apr 1996 20:16:42 +0800
To: Jeremey Barrett <jeremey@forequest.com>
Subject: Re: Is crypt(1) a prohibited export?
In-Reply-To: <Pine.BSI.3.91.960413221855.7580A-100000@newton.forequest.com>
Message-ID: <Pine.SV4.3.91.960414010416.20213C-100000@cedb>
MIME-Version: 1.0
Content-Type: text/plain


On Sat, 13 Apr 1996, Jeremey Barrett wrote:

> crypt() is a hash function, and hence is not subject to export restriction.
> (To my knowledge).

SCO (and Novell, when it was selling Unix) both shipped libcrypt.a as a 
seperate product in their development systems.  Only US and Canadian 
customers are allowed to buy the library.  Programs statically compiled
with libcrypt appear to be OK, but furineers can't have API access to
this technology :)

Dan
-- 
 Dan Busarow
 DPC Systems
 Dana Point, California

Thread