linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <orwsy2h1vf.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Sun, 17 Jun 2007 15:28:20 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Michael Poole <mdpoole@...ilus.org>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	"david\@lang.hm" <david@...g.hm>,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 17, 2007, Ingo Molnar <mingo@...e.hu> wrote:

> * Alexandre Oliva <aoliva@...hat.com> wrote:

>> On Jun 15, 2007, Ingo Molnar <mingo@...e.hu> wrote:
>> 
>> > it is a false statement on your part that the executable "does not 
>> > function properly" if it lacks that part. Try it: take out the harddisk 
>> > from the Tivo (it's a bog standard IDE harddisk), put into a nice Linux 
>> > PC, mount it, modify a bit in the kernel image header and it will likely 
>> > still boot just fine on that PC.
>> 
>> Ok, try this: take the disk out, remove/replace/modify the signature, 
>> put the disk back in, and tell me what it is that fail to run.

> you mean back into the Tivo? That is not support for what you claimed. 
> You claimed the "executable does not function properly" if it lacks that 
> part (and you did not qualify your statement with anything). That was a 
> false statement, because it still works fine in just about any 
> bog-standard PC. A true statement would be: "the modified executable 
> does not function properly _in the Tivo_". It still works fine on a 
> general purpose PC.

I stand """corrected""".  It doesn't matter, because the TiVo is where
the combination of the executable with the signature shipped, and,
see, I didn't talk about modifying the executable, what I wrote about
above was modifying the signature alone.  See?

> But you didnt really want to make use of Tivo's free software 
> enhancements, right? Lets face the sad truth: the overwhelming majority 
> of Tivo 'modders' wanted to hack the PVR not to enhance the Tivo, they 
> more likely wanted to watch pay-per-view content without the pay bit and 
> they perhaps wanted to get around service restrictions that the Tivo 
> implements (and through which it funds lower-than-production-cost for 
> the PVR).  So the 'rights' you are trying to protect are invented 
> 'rights' of mostly _freeloaders_ in fact.

Sony Betamax anyone?

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/