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: <1182244240l.11262l.0l@ecxwww1.reanet.de>
Date:	Tue, 19 Jun 2007 11:10:40 +0200
From:	Anders Larsen <al@...rsen.net>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	david@...g.hm, 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>,
	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 2007-06-18 21:50:12, Alexandre Oliva wrote:
> Given the ROM exception in GPLv3, I guess you could seal and
> anti-tamper it as much as you want, and leave the ROM at such a place
> in which it's easily replaceable but with signature checking and all
> such that the user doesn't install ROM that is not authorized by you.

Sorry, I didn't state the regulations requirement clearly enough:

The manufacturer must be able to _remotely_ update the device
firmware, so as I see it (IANAL), Tivoisation _is_ a requirement.

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