linux-kernel - Re: GPL only modules

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: <Pine.LNX.4.64.0612181134260.3479@woody.osdl.org>
Date:	Mon, 18 Dec 2006 11:42:47 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Alexandre Oliva <aoliva@...hat.com>
cc:	Ricardo Galli <gallir@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: GPL only modules

On Mon, 18 Dec 2006, Alexandre Oliva wrote:
> 
> So I guess you approve of the reformulation of LGPL as an additional
> permission on top of GPL, as in its draft at gplv3.fsf.org, right?

Yes. I think that part of the GPLv3 is a good idea.

That said, I think they are still pushing the "you don't have any rights 
unless we give you additional rights explicitly" angle a bit too hard.

The fact is, people DO have rights, regardless of what the license says. 
We have them when it comes to music, and we have them when it comes to 
software. Copyright law only gives _limited_ rights to copyright holders, 
and we should actually fight those rights being expanded, instead of 
trying to expand on them ourselves.

> > No, the sane way to think about it is that linking just creates an 
> > "aggregate" work.
> 
> That's your take on it.  It does make sense, but claiming it's *the*
> sane way to think about it is making the mistake you accused the FSF
> of making.

I did point that out at the end of the email you quote. I said it's not 
necessarily the only way to look at things. But I GUARANTEE you that it 
makes more sense than the "no rights" approach, and I GUARANTEE you that 
it makes more sense than thinking that "ld is magic, and makes a derived 
work" approach.

> In fact, it can't possibly be exempt by this paragraph in clause 2 of
> the GPL:
> 
>   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.

This is actually a red herring. The way the GPLv2 _defines_ "work" and 
"Program" is by derived "derived work". 

You're confused by _your_ interpretation of "work" and "Program". You 
think that "Program" means "binary", because that's you think normally.

But the GPLv2 actually defines that "Program" is just the "derivative work 
under copyright law".

Really. Go look. It's right there at the very top, in section 0.

In other words, in the GPL, "Program" does NOT mean "binary". Never has.

And in fact, it wouldn't make sense if it did, since you can use the GPL 
for other things than just programs (and people have).

So you _always_ get back to the question: what is "derivative"? And the 
GPLv2 doesn't actually even say anything about that, but EXPLICITLY says 
that it is left to copyright law.

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