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:	Sat, 16 Jun 2007 23:10:24 -0400
From:	Daniel Hazelton <dhazelton@...er.net>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Bron Gondwana <brong@...tmail.fm>, Ingo Molnar <mingo@...e.hu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	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 Saturday 16 June 2007 21:54:56 Alexandre Oliva wrote:
> On Jun 16, 2007, Bron Gondwana <brong@...tmail.fm> wrote:
> > I obviously wasn't clear enough.  The only way to come into complience
> > with GPL3dd4 is to reduce your ability to fix things or grant everyone
> > else the ability to mess with things.  This severely restricts you from
> > doing _anything_ in certain problem spaces due to local laws on the
> > topic, even if you're an otherwise good actor who is making worthwhile
> > source code contributions to the rest of the community.
>
> I don't know any law that requires tivoization.
>
> There may be laws that require certification or limitations on the
> user.  Manufacturer giving up the ability to make modifications would
> address this, or *perhaps* arranging for user and manufacturer to each
> hold half of the key needed to run a modification (which might comply
> with the GPLv3dd4 terms, IANAL).

It doesn't. The GPLv3 (dd4) makes that very clear. See the quote below.

"Installation Information" for a User Product means any methods, procedures, 
authorization keys, or other information required to install and execute 
modified versions of a covered work in that User Product from a modified 
version of its Corresponding Source. The information must suffice to ensure 
that the continued functioning of the modified object code is in no case 
prevented or interfered with solely because modification has been made.

DRH

> There may be business models that require the ability to make changes.
> Then it's fair to enable the user to make changes as well, such that
> they don't become dependent on the vendor, or even have their
> 1st-generation TiVo boxes left out in the cold for a while when the US
> changes the DST rules again ;-)



-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
-
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/