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: <161717d50706201634m68992ddeqb1d7557fb43c0822@mail.gmail.com>
Date:	Wed, 20 Jun 2007 19:34:28 -0400
From:	"Dave Neuer" <mr.fred.smoothie@...ox.com>
To:	davids@...master.com
Cc:	"Tomas Neme" <lacrymology@...il.com>, mdpool@...ilus.org,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On 6/20/07, David Schwartz <davids@...master.com> wrote:
>
> > Tomas Neme writes:
>
> > > I have been following this discussion for the last week or so, and
> > > what I haven't been able to figure out is what the hell is the big
> > > deal with TiVO doing whatever they want to with their stupid design.
> > > They made a design, they build a machine, they sell it as is, and
> > > provide source code for GPL'ed software... what's your problem?
>
> > It's simple: they don't provide _complete_ source code.  They keep the
> > source code for the part of their Linux kernel images that provides
> > the functionality "runs on Tivo DVRs".  The GPL requires that
> > distributors of binary versions provide complete source code, not just
> > the parts of source code that are convenient.
> >
> > Michael Poole
>
> That leads to lots of obvious nonsense unless you fix it with all kinds of
> made up ad-hoc changes just to get the result you want. Why doesn't Linus
> have to release the keys he uses to sign the Linux kernel source
> distributions? That provides the functionality "can be proven to be
> authorized by Linus". What you call "runs on Tivo DVRs", I call "can be
> proven to be authorized by Tivo to run on Tivo DVRs".

This argument is the obvious nonsense. "Runs on TiVO" is a property of
the software that TiVO distributes -- such an important property that
it would be nonsensical for them to distribute it with their hardware.
But they do distribute it, and only the GPL allows them to.

Linus' key is not required to use the software Linus distributes under
the GPL, by contrast.

>
> Tivo's choice is an authorization decision. It is similar to you not having
> root access to a Linux box. Sorry, you can't run a modified kernel on that
> machine, but you can still modify the kernel and run it on any hardware
> where authorization decisions don't stop you from doing so. The GPL was
> never about such authorization decisions.

Says judge Schwartz. Oops. That's right, you're not a judge in any
legal jurisdiction, nor an author of the GPL.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ