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: <orlkenjnxm.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Wed, 13 Jun 2007 22:59:49 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Daniel Hazelton <dhazelton@...er.net>
Cc:	Bongani Hlope <bhlope@...b.co.za>,
	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>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 13, 2007, Daniel Hazelton <dhazelton@...er.net> wrote:

> On Wednesday 13 June 2007 20:55:52 Alexandre Oliva wrote:
>> On Jun 13, 2007, Bongani Hlope <bhlope@...b.co.za> wrote:
>> > On Thursday 14 June 2007 01:49:23 Alexandre Oliva wrote:
>> >> if you distribute copies of such a program, [...]
>> >> you must give the recipients all the rights that you have

>> >> So, TiVo includes a copy of Linux in its DVR.

>> Can they modify the software in their device?

>> Do they pass this right on?

> But this *ISN'T* a right that the GPLv2 *REQUIRES* be passed on. 

You may be right.  The spirit says it should, but the legalese may
have missed the mark.  So GPLv3 makes it clear that it is.

>> It's about that copy of the kernel that ships in the device in object
>> code.  That's the one that TiVo customers ought to be entitled to
>> modify, if TiVo can modify it itself.

> The GPLv2 makes no real provision for *DIRECTLY* modifying object
> code.

Sure.  And that's not what I'm talking about.

What I'm talking about is being able to replace, upgrade, fix, tweak,
hack, and otherwise modify the program on the machine in the same way
that the vendor still can.

> What provisions the GPLv2 has apply to the source code.

This is too narrow a view of the GPLv2 provisions.

> And no, the end user *SHOULD* *NOT* be entitled to run whatever kernel they 
> like on a TiVO. It was designed with the "install new kernel" functionality 
> so that the TiVO corporation could update the kernel running on the hardware 
> when security problems came up, when bugs were fixed or even when the new 
> version gives better performance.

I.e., it was designed such that TiVo could modify the installed
kernel, but the user couldn't.  That's an outright violation of the
spirit of the GPL.

>> > Where does it say you should be able to run you modifications on the
>> > same hardware?

>> Where it says that you should pass on all the rights that you have.

>> While TiVo retains the ability to replace, upgrade, fix, break or make
>> any other change in the GPLed software in the device, it ought to pass
>> it on to its customers.

> It *DOES* *NOT* say "All rights that you have". It says "All rights
> that are granted you by this license".

I suggest you to reboot into memtest ;-)  The preamble of GPLv2 says:

  For example, if you distribute copies of such a program, whether
  gratis or for a fee, you must give the recipients
  all the rights that you have.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> If every piece of software released under the GPL had *ALL* rights
> passed on, then *ANYONE* could do the "I'm granting company X the
> right to use this software outside the GPL for $50,000USD."

The requirement above applies to licensees, not to the licensor.  The
licensor doesn't have to pass on all the rights s/he has, s/he only
decides to respect the licensee's freedoms, conditioned to the respect
of others' freedoms by means of passing on all rights the licensee has
over the software.

Arguably, one could use this argument to state that any authors of
derived works ought to pass on the right to choose the license for the
derived work under the GPL, but since (a) the above is not in the
legal terms, and (b) the downstream recipients would be bound by the
terms of the GPL anyway, and that requires the use of the GPL itself,
this would make no difference whatsoever.

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