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:02
Mike Rosing (eresrch@msn.fullfeed.com)
Wed, 13 Jan 1999 10:09:27 -0600 (CST)
On Wed, 13 Jan 1999, James Nerlinger, Jr. wrote:
> Maybe I'm missing something here -- you're bouncing from distribution of
> encrypted DATA to distribution of crypto software -- correct? A thought --
> to the best of my knowledge, if your encryption is below munitions grade,
> there is no requirement to register it or limit its distribution (correct me
> if I'm wrong). So why not simply distribute the source with low level
> encryption built in, but create the code in such a fashion as would allow it
> to be easily modified with stronger algorithms/routines? In other words,
> the enduser could add the library him/herself thereby taking the author
> outside the loop. Maybe build the package to support external compiles or
> something along those lines.
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.
The fuzzy area would be a book of bar codes which directly reads in an
executable. A very fuzzy area would be a book of bar codes that reads
out C code which could be compiled on any platform. Neither of these
methods has been tested in court.
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.
Patience, persistence, truth,
Dr. mike
The following archive was created by hippie-mail 7.98617-22 on Sat Apr 10 1999 - 01:18:02