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: <20070614111029.2a7227d9@the-village.bc.nu>
Date:	Thu, 14 Jun 2007 11:10:29 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Daniel Forrest <forrest@...g.wisc.edu>
Cc:	Chris Adams <cmadams@...aay.net>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

> I've been following this discussion and I find this interesting.
> Consider these two cases:
> 
> 1.) I ship the device back to the manufacturer, they replace the ROM,
>     and ship it back to me.
> 
> 2.) I ship the device back to the manufacturer, they load new code
>     into it, and ship it back to me.
> 
> How do these two differ?  Or is it now just a question of the ROM

Thats one thing I don't like about the GPL3 special casing.

> being in a socket?  I can't see how the technicalities of how the
> hardware is constructed can change the legality of the software.

In the replace/reflash the ROM case its about access to the righ tools -
I could do it myself, send it to another company to load my code etc.

In the Tivo case its about one company having the ability to make such
mods and blocking others from doing so.
-
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/