Re: Is crypt(1) a prohibited export?

[Jeremey Barrett <jeremey@forequest.com>]

Did the library include other encryption functions, other than one-way
functions? If so, I could see it being restricted. Linux, which is freely
available anywhere, includes a DES-using crypt() one-way hash. But since
a one-way hash function (implemented as a one way function) can't really
be used for encrypted communication, I don't think it is subject to
export restriction.

On Sun, 14 Apr 1996, Dan Busarow wrote:

> 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
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jeremey Barrett
Senior Software Engineer			jeremey@forequest.com 
The ForeQuest Company       			http://www.forequest.com/

   "less is more."
		-- Mies van de Rohe.

   Ken Thompson has an automobile which he helped design.  Unlike most
   automobiles, it has neither speedometer, nor gas gage, nor any of the
   numerous idiot lights which plague the modern driver.  Rather, if the
   driver makes any mistake, a giant "?" lights up in the center of the
   dashboard.  "The experienced driver", he says, "will usually know
   what's wrong."

		-- 'fortune` output