1995-12-06 - Re: Solution for US/Foreign Software?

Header Data

From: Rich Salz <rsalz@osf.org>
To: jimbell@pacifier.com
Message Hash: 4be9338f6078e88f78271c70b5e8c5015f45899ff2d0fb6d4cb01f6d12b986b3
Message ID: <9512062117.AA00306@sulphur.osf.org>
Reply To: N/A
UTC Datetime: 1995-12-06 21:18:46 UTC
Raw Date: Wed, 6 Dec 95 13:18:46 PST

Raw message

From: Rich Salz <rsalz@osf.org>
Date: Wed, 6 Dec 95 13:18:46 PST
To: jimbell@pacifier.com
Subject: Re: Solution for US/Foreign Software?
Message-ID: <9512062117.AA00306@sulphur.osf.org>
MIME-Version: 1.0
Content-Type: text/plain


You would not be allowed to export a browser where the crypto library is
a dynamically-loaded library.

If you wrote a "browser toolkit", you would have to take special care to
hide even the names of the crypto functions in the library symbol table.

If you want to do offshore crypto development, your best bet is to document
the required interfaces and protocols in a publication which is available to
anyone, as this is supposedly protected by the First Amendment.

On the other hand, I encourage you to try to do otherwise.
	/r$





Thread