Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752147AbXFTVnI (ORCPT ); Wed, 20 Jun 2007 17:43:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751718AbXFTVm4 (ORCPT ); Wed, 20 Jun 2007 17:42:56 -0400 Received: from gateway12.iders.ca ([206.45.72.61]:56509 "EHLO koko.iders.ca" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751326AbXFTVmz (ORCPT ); Wed, 20 Jun 2007 17:42:55 -0400 Message-ID: <46799F5B.8090101@iders.ca> Date: Wed, 20 Jun 2007 16:42:51 -0500 From: Andrew McKay User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: david@lang.hm CC: Alexandre Oliva , Alan Cox , Linus Torvalds , Al Viro , Bernd Schmidt , Ingo Molnar , Daniel Hazelton , Greg KH , debian developer , Tarkan Erimer , linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 References: <20070614235004.GA14952@elte.hu> <20070615011012.6c09066e@the-village.bc.nu> <20070615012623.GA25189@elte.hu> <20070615101007.0cbfd078@the-village.bc.nu> <4673CA7C.5040207@t-online.de> <20070616181902.GB21478@ftp.linux.org.uk> <4679557C.5080907@iders.ca> <20070620175627.319a6c55@the-village.bc.nu> <46797C52.4020907@iders.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1460 Lines: 35 david@lang.hm wrote: > On Wed, 20 Jun 2007, Alexandre Oliva wrote: > >> Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 >> >> On Jun 20, 2007, Andrew McKay wrote: >> >>> However, I don't see how this would ever require a company like Tivo >>> or Mastercard to have their networks play nice with a unit that has >>> been modified by the end user, potentially opening up some serious >>> security holes. >> >> Which is why the GPLv3 doesn't make the requirement that you stated. > > so if the BIOS checked the checksum of the boot image and if it found it > wasn't correct would disable the video input hardware but let you boot > the system otherwise it would be acceptable to you and the GPLv3? > > somehow I doubt it, but that's what it would take to prevent modified > software from interacting with their networks (remembering that these > networks are the cable and satellite networks in some cases) > > it also seems that if this was the case it would be a trivial > work-around for the GPLv3 if it was acceptable. > That is exactly where I was going with that. A trivial work around in the Tivo case. I guess GPLv4 will have to close up that hole? Andrew McKay - 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/