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: 1408b9d4eeb9781c84103a9c37943a31548915b50677fdf7e490b8999d1d3bc8
Message ID: <Pine.SV4.3.91.960414073239.21515A-100000@cedb>
Reply To: <Pine.BSI.3.91.960414014821.7867A-100000@newton.forequest.com>
UTC Datetime: 1996-04-14 16:58:50 UTC
Raw Date: Mon, 15 Apr 1996 00:58:50 +0800

Raw message

From: Dan Busarow <dan@dpcsys.com>
Date: Mon, 15 Apr 1996 00:58:50 +0800
To: Jeremey Barrett <jeremey@forequest.com>
Subject: Re: Is crypt(1) a prohibited export?
In-Reply-To: <Pine.BSI.3.91.960414014821.7867A-100000@newton.forequest.com>
Message-ID: <Pine.SV4.3.91.960414073239.21515A-100000@cedb>
MIME-Version: 1.0
Content-Type: text/plain


On Sun, 14 Apr 1996, Jeremey Barrett wrote:

> Did the library include other encryption functions, other than one-way
> functions?

The library includes the functions encrypt(3) and des_encrypt(3).  In the
US-Only version of the library each of these functions accepts a flag
value of 1 to indicate de-cryption, the export version ignores the flag,
decryption is disabled.

> On Sun, 14 Apr 1996, Dan Busarow wrote:
> > seperate product in their development systems.  Only US and Canadian 
> > customers are allowed to buy the library.

I should have said only US and Canadian customers can purchase the uncrippled
version of the library.

Dan
-- 
 Dan Busarow
 DPC Systems
 Dana Point, California






Thread