Re: Crippled Notes export encryption

At 11:50 PM 1/23/96, you wrote:
>The problem is whether you can separate the functionality of what you're
>exporting sufficiently from what you're contracting out that the exported
>material isn't a "component of a cryptosystem"; it's tough to do a good bones
>version of code if you're concerned about satisfying both the letter and
>spirit of a law to avoid hassles with the government.  On the other hand,
>if you're as big as IBM or even MIT, sometimes you can do it....

So move 100% of the development overseas.  Pick someplace where the labor
is cheaper (maybe the former Soviet Union, but I don't know what their
crypto export laws are like) and develop 100% of the product overseas.  Put
a notice inside each shrink-wrapped box that "This product was forced to be
written overseas, costing American programmers their jobs, by the
shortsightedness of Congress."


2048bit-Fingerprint: F8 A2 A5 15 56 42 9B 16  3F BD 57 0F 8A ED E3 21
No man's life, liberty or property are safe while the legislature is in session.

joe wrote:
> ...  crypto export laws are like) and develop 100% of the product
> overseas.  Put a notice inside each shrink-wrapped box that "This
> product was forced to be written overseas, costing American
> programmers their jobs, by the shortsightedness of Congress."

Better yet, specifically point to those who should be held
accountable and list the names, addresses, email address, etc. of all 
those who are involved.

Even better, where practical build into the software an option (that
you could turn on/off) which would email every piece of information
that you encrypted directly to the congressman as a kind reminder of
their position.  [This is a joke: spamming is not a good way to deal
with the issue.]

-- 
______________________________________________________________________
Corey Minter | cminter@mipos2.intel.com | (408) 765-1714
Views expressed in this message in no way represent Intel (duh).