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

Header Data

From: cmca@alpha.c2.org (Chris McAuliffe)
To: Jeremey Barrett <jeremey@forequest.com>
Message Hash: 66dacd118d0ffd719470785ab59b956082330f790359d936de8705b2f19c5667
Message ID: <199604140937.CAA26892@eternity.c2.org>
Reply To: <Pine.BSI.3.91.960413221855.7580A-100000@newton.forequest.com>
UTC Datetime: 1996-04-14 12:55:53 UTC
Raw Date: Sun, 14 Apr 1996 20:55:53 +0800

Raw message

From: cmca@alpha.c2.org (Chris McAuliffe)
Date: Sun, 14 Apr 1996 20:55:53 +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: <199604140937.CAA26892@eternity.c2.org>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

[To: Jeremey Barrett <jeremey@forequest.com>]
[cc: cypherpunks@toad.com]
[Subject: Re: Is crypt(1) a prohibited export? ]
[In-reply-to: Your message of Sat, 13 Apr 96 22:21:14 MST.]
             <Pine.BSI.3.91.960413221855.7580A-100000@newton.forequest.com> 

While not paying attention, Jeremey Barrett <jeremey@forequest.com> wrote:
>crypt() is a hash function, and hence is not subject to export restriction.
>(To my knowledge).

crypt(3) is a library routine implementing a hash function. Crypt(1) is
a general purpose cryptography program implementing an algorithm similar
to an enigma rotor machine. My question stands.

>On Wed, 10 Apr 1996, Chris McAuliffe wrote:
>> Is crypt(1) a prohibited export from the US? I thought it was. The
>> reason I ask is that it has come to my attention that HP ships that
>> overseas too, with HP-UX versions 9 and 10...

Chris McAuliffe <cmca@alpha.c2.org> (No, not that one.)

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQCVAwUBMXDCjIHskC9sh/+lAQEZ6AQAik5whxKqkICtWaD48dZigxLpCg2LgKDS
juRUVGL4bX1QvnBH9JPhnUDPB7k1y74pT3TBIUm6XD+AMMjxpH4Q6dF5iUiGWPYZ
VDVpUT1R3qQ+Bn9siR7Y3xTShg1oeLLf7T7jQ1wG0/NSV/kd0UwB89XdbrOtH48x
/9Z36ubniy4=
=JQmB
-----END PGP SIGNATURE-----





Thread