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:	Thu, 14 Jun 2007 13:37:38 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Alexandre Oliva <aoliva@...hat.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kevin Fox <Kevin.Fox@....gov>,
	Daniel Hazelton <dhazelton@...er.net>,
	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

Alexandre Oliva wrote:

> So can you please explain to me how enabling TiVO to deny others the
> freedom that it received "in kind", failing to keep with the "in kind"
> spirit of the GPL, encourage people to work together, and to merge?

They're not denying others the freedom that they themselves received. 
Tivo took GPL'd software, modified it, and distributed it with their own 
custom hardware.  You have the right to take their changes, possibly 
modify them further, and distribute them (possibly with your own hardware).

The fact that you can't modify the software and load it back onto the 
tivo is irrelevent.  They are not restricting your distribution of the 
software in any way.  Rather, they're restricting the *running* of the 
software on their proprietary hardware platform.

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