[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <orbqfdavpn.fsf@oliva.athome.lsd.ic.unicamp.br>
Date: Mon, 18 Jun 2007 16:50:12 -0300
From: Alexandre Oliva <aoliva@...hat.com>
To: david@...g.hm
Cc: Anders Larsen <al@...rsen.net>, 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 Jun 18, 2007, david@...g.hm wrote:
> they want to prevent anyone from modifying the credit card machine to
> store copies of all the card info locally.
I see. Thanks for enlightening me.
> you don't really answer this issue. since these boxes are required to
> be sealed and physically anti-tamper, changing the ROM is not
> acceptable.
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.
This would be against the spirit of the GPL, but I don't know whether
it could be interpreted as disrespecting some other provision of the
letter of GPLv3. Maybe it could. Something for lawyers to decide,
and IANAL. Something the GPLv3 folks would like to take into account,
even if the outcome may be not quite what you'd like ;-)
Thanks again for the information,
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist oliva@...d.ic.unicamp.br, gnu.org}
-
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/
Powered by blists - more mailing lists