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>] [day] [month] [year] [list]

Date:	Fri, 15 Jun 2007 13:48:32 +0200 (CEST)
From:	"Nicolas Mailhot" <nicolas.mailhot@...oste.net>
To:	"Daniel Hazelton" <dhazelton@...er.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

[Re-sending with the right subject]

>> > by your argument, the user has some "right to modify the
software", on
>> > that piece of hardware it bought which had free software on it,
correct?
>>
>> Yes.  This means the hardware distributor who put the software in
there must not place roadblocks that impede the user to get where
she wants with the software, not that the vendor must offer the
user a sport car to take her there.

>Okay. That means that if I ship Linux on a ROM chip I have to somehow
make
>it so that the person purchasing the chip can modify the copy of
Linux installed on the chip *if* I want to follow both the spirit and
the
letter
>of the GPLv2.

The key word there is "can"

You don't have to send the buyer the hardware design, replace the ROM
with a flash, use a rom socket that allows easy switching etc.

But you can not add measures to your hardware specifically designed to
stop the user from modifying the GPL software part. Especially if
those measures are something like DRM that do not make the tinkering
just technically hard, but legally forbidden.

As long as the restrictions result from technical choices not
targetted at forbidding changes you're ok.

However if the restrictions are deliberately added, have a legal
component (and legal is not "may" but absolute "can not"), that's
another thing entirely.

To take a simple example people will understand:
- everywhere around the world judges can order newspapers to publish
corrections after a slander trial
- these corrections take different forms depending on the media: in
the original article for on-line stuff, in new editions for printed
stuff

So the fact there is a legal obligation to allow judges to change
articles does not imply newspapers are forced to forgo read-only paper
prints. However editors can not refuse to change the online edition
because they have the technical possibility to do so.

"Software" change oblications (articles) are not dictating "hardware"
(read-only paper prints)

Now do anyone has a doubt how a judge would react if the newspaper
told him it wouldn't change the online edition because it's protected
by a DRM-like lock the newspaper does not want to change or share? DRM
is not a technical limitation like paper print, it's a self-imposed
artificial limitation.

-- 
Nicolas Mailhot

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