> You seem like the kind of person who could just wade through the regs
>yourself, starting at http://www.bxa.doc.gov/Encryption/Default.htm. But
>don't expect to get your answers in one sitting.
> For a definitive answer, there are lawyers with expertise in this area.
The question I am getting at is, would I get in trouble if I invented
a one-time pad XOR scheme for both sending secret messages and
encrypting personal files that used random FM noise to create the
keys. I am a Canadian and live in Canada. The people most likely
might use such a thing are Americans who travel a lot.
I am not trying to shave the law. I want to understand the spirit of
it.
--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.
Michael Amling - 20 Oct 2003 14:17 GMT
>> You seem like the kind of person who could just wade through the regs
>>yourself, starting at http://www.bxa.doc.gov/Encryption/Default.htm. But
[quoted text clipped - 5 lines]
> encrypting personal files that used random FM noise to create the
> keys.
Well, OTP has its pitfalls. Cheap but effective cryptographic random
number generating hardware would also be nice for other uses.
Other than distinguishing hardware from software and key lengths
equivalent to >56 bits symmetric from key lengths <=56 bits, the regs
don't much care what the encryption technique is.
> I am a Canadian and live in Canada. The people most likely
> might use such a thing are Americans who travel a lot.
US export regulations don't apply to you if you're not exporting any
crypto from the USA. If your customers tell you credibly that it's for
their own use and not for reexport, you're as much off the hook as
distributors of 128-bit browsers are.
> I am not trying to shave the law. I want to understand the spirit of
> it.
We would all like to see a concise cogent version of the regulations,
a summary, a generalization, a spirit.
--Mike Amling