[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46738CD2.2080804@dgreaves.com>
Date: Sat, 16 Jun 2007 08:10:10 +0100
From: David Greaves <david@...eaves.com>
To: Krzysztof Halasa <khc@...waw.pl>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Daniel Hazelton <dhazelton@...er.net>,
Michael Gerdau <mgd@...hnosis.de>,
Alexandre Oliva <aoliva@...hat.com>,
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
Krzysztof Halasa wrote:
> David Greaves <david@...eaves.com> writes:
>
>> This 5 minute design undoubtedly has flaws but it shows a direction:
>> A basically standard 'De11' PC with some flash.
>> A Tivoised boot system so only signed kernels boot.
>> A modified kernel that only runs (FOSS) executables whose signed hash
>> lives in the flash.
>
> How hard would it be to reprogramm the flash?
The flash contains hashes signed by the companies private key.
The kernel contains the public key. It can decrypt the hashes but the private
key isn't available to encrypt them. So although you can put a new application
onto the system, you can't create a signed hash to write to the flash.
The kernel only runs the executable if the hash is valid.
You can re-write the kernel to avoid this check - but the hardware is Tivoised -
so you can't run it.
I am not suggesting the kernel should go down the GPLV2 route - I am wondering
if this is a viable scenario or one of Schneiers' "movie-plot" threats :)
David
-
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