Other Directory Sites: SeekWonder | Directory Owners Forum
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:15:19
Adam Back (aba@dcs.ex.ac.uk)
Sat, 3 Oct 1998 23:53:01 +0100
Paul Jarc writes:
> > The problem is that due to the United States export rules, I cannot
> > export Crypto software, which means I must legally put a restriction
> > on any Crypto code I write.
>
> Must you? I would think that that restriction is already in place,
> and is put there by the U.S. government, not by you.
There was something extra to ITAR (not sure if it is in the EARs)
about it being the munitions manufacturers duty to ensure that the
arms didn't get exported. The _manufacturer_ could be prosecuted if
it was found that an export occured because of his negligence.
That sounds like it's aimed at bombs, etc. but as we know it applied/s
to crypto software also.
So, no I don't think just adding a "btw. the USG has some dumb idea
that you can't export this" will cut it unless you fancy taking the
risk that someone goes right ahead and exports it, and the USG decides
to make something of it.
Recall PRZ himself did not export anything, and yet the Feds were
building the case on the basis that he allowed it to be exported, or
did not try hard enough to prevent it being exported. Rumor has it
that a low profile cypherpunk type, Kelly Goen, had something to do
with it, and he was the lesser publicized 2nd defendent in the USG
investigation of PRZ and associate.
Perhaps Peter, or another of the lawyers (on Peter Junger's)
softspeech list) could comment on the legal accuracy of the above, and
continued relevance with EAR regulations.
Yeah, might as well put the topical sig in. Don't export now :-)
Adam
--
print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:15:19