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: <2e6659dd0706210553p5a854ad7yc8915818b358a27c@mail.gmail.com>
Date:	Thu, 21 Jun 2007 09:53:54 -0300
From:	"Tomas Neme" <lacrymology@...il.com>
To:	"david@...g.hm" <david@...g.hm>
Cc:	"Alexandre Oliva" <aoliva@...hat.com>,
	"Andrew McKay" <amckay@...rs.ca>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Al Viro" <viro@....linux.org.uk>,
	"Bernd Schmidt" <bernds_cb1@...nline.de>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Daniel Hazelton" <dhazelton@...er.net>,
	"Greg KH" <greg@...ah.com>,
	"debian developer" <debiandev@...il.com>,
	"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

> > as long as this right is not used by the software distributor to
> > impose restrictions on the user's ability to adapt the software to
> > their own needs.  The GPLv3 paragraph above makes a fair concession in
> > this regard, don't you agree?
>
> no, one of the rules for the network is that the software must be
> certified, you are requireing the device to permit the software to be
> changed to an uncertified version.(to store credit card numbers and send
> them to a third party for example)

Also another way of doing this is having every network ask the kernel
for its key, and checking it. If it doesn't match a certified key,
then not allowing you to access the network.

Besides the fact that this would be a very costly approach, having
every network needing to update their certified keys list every time
TiVo and every other DVR vendor updates their kernels, it would also
prevent any form of modified software to give you any of the TiVo's
expected functionality: it would load, you would be able to play pong
on it, but not watch or record TV, and they can't be blamed for it,
because if the kernel's been tampered with, it might have been made so
it saves the video unencrypted on the Harddrive, and it certainly *is*
the network's right to stop you from doing so. So what the fuck do you
want from them?

T

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