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:	Mon, 18 Jun 2007 19:03:09 -0700
From:	"David Schwartz" <davids@...master.com>
To:	"Alexandre Oliva" <aoliva@...hat.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

> The box could even be sold by third party vendors, I think they may even
> have started off that way, my old Series 1 had a big Philips logo on it.
> So now we make sure that this hardware refuses to boot any unsigned
> code, but it wasn't shipped containing GPLv3 software, so it's license
> terms simply does not apply.
>
> The software is shipped on a ROM card which can no longer be modified by
> the manufacturer or any third party, so it would seem to comply with the
> GPLv3. I can even imagine that the hardware is really general purpose
> but the ROM is encrypted so that only the BIOS/bootloader can unlock it.
>
> So the GPLv3 seems to fall short on actually preventing tivoization. It
> just requires an extra layer of indirection, ship hardware seperately
> from software.
>
> Jan

If this flaw is still the latest GPLv3 drafts, it should be fixed. It's a
simple, technical error that can easily be rectified.

I don't have the latest draft handy, but my recollection is that it talks
about software that is "transferred along with" hardware. What it should say
is object code that contains activation logic for hardware.

That is, if I ship the Linux kernel (assuming for the moment the Linux
kernel was under GPLv3) with special activation logic to run on platforms X,
Y, and Z, then the source code should have to include how to make my changes
have that same special activation logic for those same platforms.

If the GPLv3 doesn't do that, it's broken.

Note that I'm not opining on whether this is a good thing or a bad thing.
But people who choose the GPLv3 because they want to prohibit tivoization of
their software should in fact get that prohibition.

DS

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