Other Directory Sites: SeekWonder | Directory Owners Forum
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:18:03
James Nerlinger, Jr. (jnj@ais-bbs.org)
Wed, 13 Jan 1999 13:32:44 -0500
>Any export of _executable_ crypto code has to be registered. "Computer
>readable" crypto code is supposed to be registered to certain countries,
>it is considered "technology transfer" (i.e. you may be teaching the bad
>guys how to do it them selves). Exporting a book has no restrictions.
I suppose I should have clarified that statement -- thanks for the
correction, Mike.
>AFAIK Bersteine's (sp?) case is still pending, so it isn't clear yet that
>code can be posted to a web page. This is both human and machine
>readable. The government would prefer it isn't possible, but so far they
>have lost every time. AS far as I'm concerned, posting C code on a web
>page is the same as writing a book. So that's what I do.
This is more along the lines of what I was referring to as far as the actual
code is concerned.
Another thought I referenced was designing a program that would load
external modules for its encryption routines. This would allow a fully
compiled program to be distributed generally, then the crypto libraries
would be distributed separately. Shouldn't be too difficult to design I
would think and it would allow for a maximum amount of configurability and
growth for the product as whenever a new crypto library came out, it could
simply be appended to the program -- a sort of crypto plug-in so to speak.
James
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:18:03