[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706210929110.31603@asgard.lang.hm>
Date: Thu, 21 Jun 2007 09:30:29 -0700 (PDT)
From: david@...g.hm
To: Tomas Neme <lacrymology@...il.com>
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
On Thu, 21 Jun 2007, Tomas Neme wrote:
>> > 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.
no, this doesn't work becouse if the software has been altered you don't
know if the key it's giving you matches that software. it could be giving
you the key from the unmodified software.
David Lang
-
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/
Powered by blists - more mailing lists