[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: propose: `cypherpunks license' (Re: Wanted: Twofish source code) (fwd)
Forwarded message:
> Subject: Re: propose: `cypherpunks license' (Re: Wanted: Twofish source code)
> From: Derek Atkins <[email protected]>
> Date: 30 Sep 1998 16:02:23 -0400
> The big issue I see with GPL and Crypto software is that with the GPL
> you cannot add any redistribution restrictions. 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. But, this is a "further restriction" as far as the
> GPL is concerned. This, in turn, means I cannot use the GPL for
> Crypto software.
A legal prohibition isn't a licensing restriction, it's a distribution
restriction. A license restriction defines who can use a product and
under what terms they may do so legaly, it doesn't address where they
may use it legaly.
If you tried to put a license restriction that said "can only be used in
the US" *then* you would be correct. It isn't the copyright holders choice
and therefore they're not responsible for it per se. Not to mention that
it would be very hard to support legaly.
A good example is I have a military book that says that you can only
possess the book in the US and Canada...try to enforce that one.
Were that the case Phil Z. would be sittin in a hoosgow right now.
Personaly, I like the idea of printing your source out and sending it to
HackTick for typing in and reposting. That wouldn't effect your initial
licensing restrictions and bypasses the restrictions handily.
____________________________________________________________________
The seeker is a finder.
Ancient Persian Proverb
The Armadillo Group ,::////;::-. James Choate
Austin, Tx /:'///// ``::>/|/ [email protected]
www.ssz.com .', |||| `/( e\ 512-451-7087
-====~~mm-'`-```-mm --'-
--------------------------------------------------------------------