🚀 go-pugleaf

> Apparently there ARE export controls on public domain information.
> For example, the DES encryption algorithm is in the public domain,
> but the export of DES encryption programs is strictly forbidden,
> even to our friends in Great Britain.
> 
> The products that my company, Sun Microsystems, ship overseas do not
> include des(1) or crypt(1). Crypt(1) has been a standard part of Unix
> for many years and methods for breaking it have been known for years.
> It provides minimal security. I was told that we are forbidden
> by the State Department to export those from the U.S. even though
> the algorithms are in the public domain.
> 
...
> So what's the deal? Is there any logic or reason to the export 
> restrictions? Or do I have my facts wrong?
> 
> 	Kent Klinner
> 	Sun Microsystems

The restrictions are ludicrous.  You can get the DES encryption document
here in Canada -- I have it as an appendix in a computer science textbook of
mine.  If that is sufficient to write a DES encryptor, then any export
controls on programs containing such an encryptor are futile.

The restriction on exporting crypt is even more laughable.  We've used it in
Canada for years; the machine that I'm writing on has it.

DES and crypt are *already* out of American hands.  Export restrictions on
those particular algorithms seem to be pointless hassling of American
firms by the State Department.

						
						Jim Tubman
						(From the account of
						 Tim Brecht)
						University of Saskatchewan
						Canada