From owner-freebsd-advocacy Thu Jun 28 17: 1:19 2001 Delivered-To: freebsd-advocacy@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id D5CAD37B406 for ; Thu, 28 Jun 2001 17:01:15 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: (from nobody@localhost) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) id f5T018S14841; Thu, 28 Jun 2001 17:01:08 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: Ted Mittelstaedt X-Authentication-Warning: mail.freebsd-corp-net-guide.com: nobody set sender to tedm@toybox.placo.com using -f To: Rahul Siddharthan Subject: Re: FreeBSD and Microsoft Message-ID: <993772867.3b3bc543b74ab@mail.freebsd-corp-net-guide.com> Date: Thu, 28 Jun 2001 17:01:07 -0700 (PDT) Cc: Ted Mittelstaedt , FreeBSD Advocacy References: <20010628111710.E9802@lpt.ens.fr> <001b01c0ffb7$2525b4a0$1401a8c0@tedm.placo.com> <20010628115803.G9802@lpt.ens.fr> In-Reply-To: <20010628115803.G9802@lpt.ens.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 205.139.102.133 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quoting Rahul Siddharthan : > > The GPL is not incompatible with selling a boxed distribution, but it > is incompatible with a "per seat" license. You can sell it to A, but > you can't stop A from further redistributing it, or insist that it can > be installed only on one machine (or used only by one user). > True, but you can say that unless B buys a registered copy of the GPL code from you that they don't get support. Or more interestingly, it might be quite possible to write a module that provides some critical function that is distributed as binary only and that requires some kind of encrypted key exchange between a server you control on the Internet and itself. Then you could modify the GPL code to exchange data with that module using a pipe or script or some such. Depending on the app and how you wrote it, I think you could make serialization difficult enough to break that most people wouldn't make the effort. Naturally, someone could simply read the GPL modifications and rewrite the module you wrote under GPL, but they already do that anyway when people write GPL programs that are functionally identical to commercial programs. With enough ingenuity, someone could defeat the intent of the GPL on a particular piece of software, with value-added software that is a separate module that is separately licensed. As Terry said it would greatly increase administrative overhead because of all the auditing you would have to do, but the GPL is no panacea in this regard. - indeed one of the reasons for the FreeBSD ports system is to sidestep all of the rediculous redistribution requirements that a number of packages place on themselves. Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message