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 for Android: free password hash cracker in your pocket

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

Message-ID: <ortzt7htms.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Sun, 17 Jun 2007 05:28:43 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Scott Preece <sepreece@...il.com>, 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

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

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

>> > if the manufacturer believes that it cannot legally allow software 
>> > modification, all the restriction does is force them either to make 
>> > the software unmodifiable (which advances freedom not at all) or to 
>> > use software under a different license (which advances freedom not 
>> > at all).
>> 
>> Right.
>> 
>> But if the manufacturer believes that it can legally allow it, and 
>> wants to be able to install, software modifications, then it must 
>> decide between giving that up and letting the user do it as well.  And 
>> this is where the users interests may prevail.

> with the little tiny problem that this is not what the GPLv3 actually 
> implements.

Except that it does.  Go read it, then come back and admit you were
mistaken and spreading lies about it.

The vendor must decide between respecting the freedom of the user, or
stopping itself from modifying the software too.

> But most fundamentally, a license should _never_ get into the 
> business of trying to 'judge' what _use_ is 'good' and what is 'evil'. 

What it does is to seek to carry out its mission (*) of defending
users' freedoms.  Obstacles that are placed to impede the user from
enjoying the freedoms are supposed to not be permitted by the GPL.

(*) it seems that understanding "spirit of a license" is very
difficult for you; does the term "mission" help you understand what
the GPL means when it says "similar in spirit"?

> But the GPLv3 completely destroys Tivo's ability to use Linux, were
> Linux to be under the GPLv3.

Sorry, wrong.  Barring nonsense.

> You tried to find a workaround for that, by suggesting the 'dont do 
> security fixes then', 'use a split key', 'use a rent model' solutions, 

FTR, rent model wasn't me, and it doesn't escape the GPLv3dd4
obligations IIUC, IANAL.

> but dont you realize that by suggesting those you are explicitly against 
> the intent of RMS, who wants to _stop_ Tivo from being able to do DRM? 

You misunderstand not only the spirit of the license, but his
intentions.  Oh, wait!  They're the same, that's why.

Respect and defend users' freedoms.

Repeat after me until it sinks.

I know you're not stupid.  Why do you pretend to be?

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