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: <alpine.LFD.0.98.0706140923250.14121@woody.linux-foundation.org>
Date:	Thu, 14 Jun 2007 09:32:24 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Kevin Fox <Kevin.Fox@....gov>
cc:	Daniel Hazelton <dhazelton@...er.net>,
	Alexandre Oliva <aoliva@...hat.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	"david@...g.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 Thu, 14 Jun 2007, Kevin Fox wrote:
> 
> The hardware isn't directly covered by the GPL, correct. But, if they
> want to use the software on the hardware, they have to comply with the
> GPL.

Only with the GPLv3.

Again, don't confuse the *new* requirements in the GPLv3 with any "GPL 
requirements". They didn't exist before. The kernel never signed up to 
them. They are irrelevant for the discussion.

So hardware details have *nothing* to do with compying with the GPLv2.

Could you write *another* license that puts limitations on the hardware or 
environment that you have to comply with? Sure can. And the GPLv3 does 
that. But the GPLv2 does not, and that's a fundmanetal *improvement* over 
the GPLv3 in my opinion.

Do you like licenses that force the licensee to give money back?

So why do you like licenses that force the licensee to give access to 
hardware back? It's a form of "extra compensation" that the GPLv2 never 
had. The GPLv2 talks about giving access to the *source* code. The GPLv3 
talks about giving access to the *hardware*. 

Can people really not see the difference, and why I might think it's a 
fundamental difference, and why I might choose to say that the GPLv3 is a 
worse license?

And *why* would I ever downgrade to a worse license? There had better be 
some really pressing reason to choose the worse version of the GPL. And I 
just don't find that reason in the GPLv3 itself - although, as mentioned, 
the reason could become *external* (ie I might accept a worse license it 
it comes with external code attached to it that I think makes up for the 
license deficiency).

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