linux-kernel - RE: [PATCH] Ban module license tag string termination trick

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:	Sat, 3 Feb 2007 23:56:43 -0800
From:	"David Schwartz" <davids@...master.com>
To:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] Ban module license tag string termination trick

> On Feb 3 2007 10:31, David Schwartz wrote:
> >
> >The way out of the GPL problem is to make clear that it is *not* a
> >copyright enforcement scheme
>
> So why do we have EXPORT_SYMBOL_GPL then, if
>
>   -  there shall be no enforcement (such as requiring modules to carry
>      exactly one MODULE_LICENSE, and it be GPL to access GPL symbols)
>
>   -  EXPORT_SYMBOL_GPL can be circumvented by having multiple
>      MODULE_LICENSE and one of those MODULE_LICENSE is ("GPL")
>      [see Bodo's patch]

The same reason we do any other checks. Why don't we let a normal use list
the contents of any directory they want to? Because we believe that allowing
people to do that, in the default shipping configuration, has disadvantages
that outweight the benefits. If someone disagrees, they are free to remove
the check or bypass it or whatever, by then they take those risks.

> I think Linus has made a stance on the purpose of _GPL [yup,
> http://lkml.org/lkml/2003/12/4/84 ], and I interpret his words "if you
> need this export, you're clearly doing something that requires the GPL"
> being in conflict with [X].

Exactly. It conveys the opinion of whoever set the tag that they believe it
is difficult to impossible to use that symbol in anything other than a
derived work. It is, to some extent, misnamed because the GPL does not
require all derived work to be placed under the GPL. (For example, a derived
work that is never distributed need not be placed under the GPL.)

> Note IANAL, more a developer, so please don't flame too much.

No, you're dead on.

Why don't we allow a normal user to unlink any file? Because the person who
put in the check to prevent that believes that that's not something you
should be doing. If you *want* to do it, it's your right. But it is also
their right to put in the code that stops you, so that you have to *want* to
do it in order to do it.

The GPL allows me to add code and distribute and it allows you to remove
that same code if you want. If you disagree with my judgment, you may bypass
it at your own risk.

DS

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