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]

Date:	Thu, 14 Jun 2007 15:55:41 -0500
From:	Chris Adams <cmadams@...aay.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

Once upon a time, Alexandre Oliva  <aoliva@...hat.com> said:
>> What the GPL *does* say is that you can't "add additional
>> restrictions to the license"
>
>Not quite.  It's more general than that:
>
>  You may not impose any further restrictions on the recipients'
>  exercise of the rights granted herein.

GPLv2 section 0 says:

  Activities other than copying, distribution and modification are not
  covered by this License; they are outside its scope.  The act of
  running the Program is not restricted, ...

The license does not cover running of the program.  It doesn't restrict
it, but it doesn't cover it.  Claiming otherwise is turning the GPL into
yet another dreaded EULA.

Nowhere does the GPLv2 define modification as "modify and run in place".
The Preamble emphasizes sharing; hardware is a fixed object and can't be
shared in the same fashion as software.

Also, GPLv2 section 2 includes:

  In addition, mere aggregation of another work not based on the Program
  with the Program (or with a work based on the Program) on a volume of
  a storage or distribution medium does not bring the other work under
  the scope of this License.

TiVo's firmware (and any restrictions it may carry) is not affected by
the GPLv2.

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