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: <or4plbjlr9.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Wed, 13 Jun 2007 23:46:50 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Chris Adams <cmadams@...aay.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 13, 2007, Chris Adams <cmadams@...aay.net> wrote:

> Once upon a time, Alexandre Oliva  <aoliva@...hat.com> said:
>> if you distribute copies of such a program, [...]
>> you must give the recipients all the rights that you have

>> So, TiVo includes a copy of Linux in its DVR.  

>> TiVo retains the right to modify that copy of Linux as it sees fit.

>> It doesn't give the recipients the same right.

> Sure it does; you received a program (the kernel) and you can modify it.

If I take the software I received, build it and install it on the same
hardware, it won't run.  Something is missing in the source code I
received, I guess..

If I make changes to the source code, build it, and install it on that
same computer, it won't run.  How is that being able to modify *that*
copy of the program?

If TiVo makes the same changes, builds tehm, and installs it on my
computer, it will run just fine.  How are they passing on the right
they had to me?

> You also received hardware; they don't support modification of that.

They don't have to support them.  They don't have to help me if it
breaks.  But if they can do it and I can't, they're failing to comply
with the spirit of the GPL.

> Nowhere in the license does it say they have to, because the license
> only covers the program.

They can't distribute the program while imposing restrictions on
modification not present in the software license itself.

> Or are you claiming that putting software on hardware makes the result a
> derivative work?  I think it falls under the "mere aggregation" clause.

I tend to agree, in this particular case, but IANAL.  I don't rule out
derivative works in future attempts to find loopholes in the GPL.

> What if TiVo had put the kernel in a burned-in ROM

Then they wouldn't have the ability to change it any more, so there
wouldn't be such a right to pass on to the users.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ