Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751936AbXBBKsL (ORCPT ); Fri, 2 Feb 2007 05:48:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751897AbXBBKsL (ORCPT ); Fri, 2 Feb 2007 05:48:11 -0500 Received: from embla.aitel.hist.no ([158.38.50.22]:36965 "HELO embla.aitel.hist.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751936AbXBBKsJ (ORCPT ); Fri, 2 Feb 2007 05:48:09 -0500 Message-ID: <45C3164C.1050805@aitel.hist.no> Date: Fri, 02 Feb 2007 11:45:32 +0100 From: Helge Hafting User-Agent: Icedove 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: davids@webmaster.com CC: sofar@foo-projects.org, Linux Kernel Mailing List Subject: Re: [PATCH] Ban module license tag string termination trick References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1113 Lines: 28 David Schwartz wrote: > In any event, even if you assume it is a copyright enforcement scheme, it is > not circumvention to remove or disable such a scheme with the permission of > the copyright holder. Section 2 of the GPL grants just such permission. > The way I see this: There is a copyright enforcement scheme. (A simple test for the word GPL.) Trivial, but still an enforcement scheme. You are of course allowed to remove the test completely, as the GPL lets you change the kernel source in any way you wish. But you are still not allowed to circumvent the scheme as long as it is in place - in those parts of the world were circumventing is illegal. So a vendor using the \0 trick is on very shaky ground. He has another option - to patch out the test. But he don't want that, for then he have to distribute a kernel, not only a module. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/