1998-09-28 - Re: GPL & commercial software, the critical distinction (fwd)

Header Data

From: Adam Shostack <adam@homeport.org>
To: Jim Choate <cypherpunks@EINSTEIN.ssz.com>
Message Hash: 13f8b04adb695da1605887ed75d6b84853189992c8512d9386bf3f150d5b1ad3
Message ID: <19980929081450.A3534@weathership.homeport.org>
Reply To: <199809290009.TAA03654@einstein.ssz.com>
UTC Datetime: 1998-09-28 23:23:16 UTC
Raw Date: Tue, 29 Sep 1998 07:23:16 +0800

Raw message

From: Adam Shostack <adam@homeport.org>
Date: Tue, 29 Sep 1998 07:23:16 +0800
To: Jim Choate <cypherpunks@EINSTEIN.ssz.com>
Subject: Re: GPL & commercial software, the critical distinction (fwd)
In-Reply-To: <199809290009.TAA03654@einstein.ssz.com>
Message-ID: <19980929081450.A3534@weathership.homeport.org>
MIME-Version: 1.0
Content-Type: text/plain



On Mon, Sep 28, 1998 at 07:09:51PM -0500, Jim Choate wrote:
| 
| The problem with your interpretation is that in a sense you want your cake and
| eat it too. In short you want to be able to use somebody elses code in your
| product without their having a say in how their code is used or receiving a
| cut of the profits. The GPL/LGPL is specificaly designed to prevent this.


	I'll suggest that in a security context, having ones cake and
eating it too may not be such a bad thing.  If I can develop a
commercial product with crypto code thats been made available to the
community, then there is a lower chance the code will contain bogosity 
in its security critical functions.

	The GPL (not the LGPL) specifically prevents this with the
best of intentions.

Adam

-- 
"It is seldom that liberty of any kind is lost all at once."
					               -Hume






Thread