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: <20070615072322.GA7594@brong.net>
Date:	Fri, 15 Jun 2007 17:23:22 +1000
From:	Bron Gondwana <brong@...tmail.fm>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Bron Gondwana <brong@...tmail.fm>, Ingo Molnar <mingo@...e.hu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	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 Fri, Jun 15, 2007 at 02:38:41AM -0300, Alexandre Oliva wrote:
> On Jun 15, 2007, Bron Gondwana <brong@...tmail.fm> wrote:
> 
> > #define Dell CFG_FAVOURITE_VENDOR
> 
> > A Dell desktop machine is a piece of hardware.  The manufacturer has the
> > source code (hypothetically) to the BIOS.  The BIOS is required for the
> > machine to boot and run Linux.
> 
> > Riddle me this (especially Alexandre, I'm just latching on to Ingo's
> > post because it has the right hook to grab) - are Dell required to give
> > out the source to the bios to enable people to have the same rights Dell
> > engineers do to modify the behaviour of the system?
> 
> What is the license for the bios?  Does it say anything about 'no
> further restrictions on the freedoms to modify and share the
> software'?

It's a necessary part of the boot process, without which Linux could
not be started.  Indeed, the Linux kernel interacts with it through a
(loosely, incompletely and frequently buggy) documented interface, much
like how binary modules interact with the linux kernel (even if they do
get loaded into the sacred ring0 execution space, ooh err)

What happens if you're debugging something you think is a bug in the
Linux kernel and then you run bang into some interactions that make you
think the bug might be in the BIOS instead.  Oh unhappy day, you don't
have access to the source code to the BIOS so you can't check.  Those
cretins at Dell (does a #define still work when it's 2 levels quoted?)
have denied your freedom to modify and debug the system they sold you
which is based _in_a_large_part_ on the GPL$mumble Linux kernel and
hence needs to be interoperable.

Regardless of your sophistry, it's a slipery slope by which Dell could
be forced to exert their corporate might back up the tree to the BIOS
vendor and get the right to release that BIOS source code to you or
stop distributing Linux on their machines. 

> Does it include any mechanisms to stop people from booting modified
> versions of the Linux that ships with the machine?

Maybe, and either way, a future update could, and you couldn't undo it
unless the BIOS flash system lets you "downgrade" again.

Bron.

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