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]

Date:	Sun, 17 Jun 2007 09:38:20 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Rob Landley <rob@...dley.net>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, 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

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

> On Jun 15, 2007, Ingo Molnar <mingo@...e.hu> wrote:
> 
> >>> it irreversibly cuts off certain people from being to distribute
> >>> GPLv3-ed software alongside with certain types of hardware that 
> >>> the FSF's president does not like.
> >>>
> >> That's not true.  They can just as well throw the key away and 
> >> refrain from modifying the installed software behind the users' 
> >> back.
> 
> > uhm, so you claim that my argument is false, and your proof for that 
> > is a "non-upgradeable Tivo"?? <sarcasm> That is a _great_ idea. Not 
> > being able to patch security holes. Not being able to fix bugs. Not 
> > being able to add new features. Makes complete sense.
> 
> Oh, so you think patching security holes, fixing bugs and adding new 
> features are good ideas?  What if you can't do it in your TiVo?

this has to be one of the most bizarre arguments i've read in this 
thread as of date. Are you seriously questioning the notion that it's a 
good and legitimate idea for a hardware vendor to make the system 
fixable, patchable and upgradable? Are you seriously suggesting that for 
a hardware vendor to be able to offer such a solution, if they are under 
the unescapable restriction of content providers that the system itself 
must be tamper-proof, it should not be able to use a GPL-ed kernel at 
all? Because that is what your arguments lead to, and that is what the 
GPLv3 implements. In case you didnt notice: RMS _does not want the Tivo 
to use a GPLv3 kernel_, simple as that, and the GPLv3 achieves that. He 
wants Tivo to either to go out of business or to go to WinCE or some 
other OS. Did you ever think about the meaning of the "anti" word in the 
"anti-Tivo" expression? Hint: it's not some friendly suggestion of 
cooperation and working together ;)

	Ingo
-
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/