LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <sofar@foo-projects.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Ban module license tag string termination trick
Date: Fri, 2 Feb 2007 00:24:48 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKOEBOBFAC.davids@webmaster.com> (raw)
In-Reply-To: <45C27908.1000202@foo-projects.org>


> to me it even screams "bypassing or a digital copyright
> enforcement system".
> that sounds really close to "D.M.C.A. violation" :)
>
> thank goodness I'm not a laywer...

It is not. GPL export is *not* a copyright enforcement scheme. (See the many
times when this was discussed on this list.) The GPL prohibits the use of
copyright enforcement schemes in sections 6 and 7.

Suppose there were some law that said that if I put "do not modify this
line" in a piece of code, you could not modify that line. The GPL would
clearly prohibit putting such a thing in a work, as that would remove from
recipients their right to modify the code -- a right guaranteed to them
under the GPL.

Same with GPL export. If it is a copyright enforcement scheme and it
prevented people from modifying the code to include the license tag
termination trick, they would not have the right to modify the code that way
which the GPL says they are supposed to have. So *if* EXPORT_GPL were a
copyright enforcement scheme, the Linux kernel containing it could not be
distributed.

The consensus view, as I understand it, is that the GPL export is a
warning/notification scheme to alert people that their use of these symbols
in non-GPL code is believed to violate the GPL *if* that code is distributed
(which the GPL export logic has no way to determine has happened or will
ever happen). It is no different than refusing a command to change the time
of day from a non-superuser.

In any event, even if you assume it is a copyright enforcement scheme, it is
not circumvention to remove or disable such a scheme with the permission of
the copyright holder. Section 2 of the GPL grants just such permission.

DS



  reply	other threads:[~2007-02-02  8:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28  0:41 [PATCH] Blacklist hsfmodem module Alexey Dobriyan
2006-11-01 11:21 ` Jan Engelhardt
2007-02-01 21:20   ` [PATCH] Ban module license tag string termination trick Jan Engelhardt
2007-02-01 21:28     ` [m-i-t part] " Jan Engelhardt
2007-02-01 21:55     ` [PATCH] " Randy Dunlap
2007-02-01 22:17     ` Jon Masters
2007-02-01 22:30       ` Trent Waddington
2007-02-01 23:34         ` Auke Kok
2007-02-02  8:24           ` David Schwartz [this message]
2007-02-02 10:45             ` Helge Hafting
2007-02-03 18:31               ` David Schwartz
2007-02-03 20:47                 ` Jan Engelhardt
2007-02-03 22:21                   ` Alan
2007-02-03 23:32                     ` Jon Masters
2007-02-04  0:05                       ` Alan
2007-02-04  7:56                   ` David Schwartz
2007-02-07 12:18                 ` Helge Hafting
2007-02-07 18:56                   ` David Schwartz
2007-02-12 15:50                     ` Helge Hafting
2007-02-12 16:42                       ` Alan
2007-02-12 22:37                       ` David Schwartz
2007-02-02  0:17       ` Tomas Carnecky
2007-02-02  0:51         ` Trent Waddington
2007-02-02  2:19           ` Valdis.Kletnieks
2007-02-02  3:12           ` Arjan van de Ven
2007-02-02  6:15             ` Jon Masters
2007-02-02 14:53     ` Paul Rolland
2007-02-02 15:11       ` Jan Engelhardt
2007-02-02 16:53         ` Randy Dunlap
2007-02-02 17:41           ` Jan Engelhardt
2007-02-02 17:49             ` Randy Dunlap
2007-02-02 19:06               ` Jan Engelhardt
2007-02-03  1:12                 ` Randy Dunlap
2007-02-03  1:29                   ` Jan Engelhardt
2007-02-02 18:37         ` Paul Rolland
2007-02-02 19:08           ` Jan Engelhardt
2007-02-04  8:14             ` Paul Rolland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MDEHLPKNGKAHNMBLJOLKOEBOBFAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sofar@foo-projects.org \
    --subject='RE: [PATCH] Ban module license tag string termination trick' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).