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: <MDEHLPKNGKAHNMBLJOLKKEJFGNAC.davids@webmaster.com>
Date:	Mon, 17 Sep 2007 08:20:39 -0700
From:	"David Schwartz" <davids@...master.com>
To:	"Theodore Tso" <tytso@....edu>, "Krzysztof Halasa" <khc@...waw.pl>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Can E. Acar" <can.acar@...-g.com.tr>, <misc@...nbsd.org>,
	<linux-kernel@...r.kernel.org>,
	"Daniel Hazelton" <dhazelton@...er.net>,
	"Eben Moglen" <moglen@...twarefreedom.org>,
	"Lawrence Lessig" <lessig_from_web@...ox.com>,
	"Bradley M. Kuhn" <bkuhn@...twarefreedom.org>,
	"Matt Norwood" <norwood@...twarefreedom.org>
Subject: RE: Wasting our Freedom


Theodore Tso writes:

> Now, you don't need a licence from the original author to use
> the derived work. The author of the derived work only needs
> a licence from the original author to create a derived work.
> Do you think Microsoft users have licences from authors of
> the works MS Windows etc. are based on? :-)

Of course you don't need a license to *use* the derived work. You never need
a license to use a work. (In the United States. Some countries word this a
bit differently but get the same effect.)

If, however, you wanted to get the right to modify or distribute a
derivative work, you would need to obtain the rights to every protectable
element in that work. If the work were under a GPL or BSD type license, only
the original author of each individual element could grant you such a
license.

Read GPL section 6, particularly this part: "Each time you redistribute the
Program (or any work based on the Program), the recipient automatically
receives a license from the original licensor to copy, distribute or modify
the Program subject to
these terms and conditions."

To distribute a derivative work that contains protectable elements from
multiple authors, you are distributing all of those elements and need the
rights to all of them. You need a license to each element and in the absence
of any relicensing arrangements (which the GPL and BSD license are not),
only the original author can grant that to you.

It is a common confusion that just because the final author has copyright in
the derivative work, that means he can license the work. He cannot license
anyone else's creative contributions absent a relicensing arrangement.

The GPL is explicit that it is not such a license. That's what the "from the
original licensor" language in section 6 means. The BSD license is not
explicit, but it couldn't work any other way.

When you receive a Linux kernel distribution, you receive a GPL license to
every protectable element in that work from that element's individual
author. Nobody can license the kernel as a whole to you.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ