linux-kernel - Re: Fwd: That whole "Linux stealing our code" thing

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: <WorldClient-F200709030221.AA21100013@webmaster.com>
Date:	Mon, 03 Sep 2007 02:21:10 -0700
From:	"David Schwartz" <davids@...master.com>
To:	linux-kernel-owner+davids=40webmaster.com-S1754697AbXICI7Q@...r.kernel.org,
	"Jeff Garzik" <jeff@...zik.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: That whole "Linux stealing our code" thing

Jeff Garzik wrote:

> Secondary parties have the power to grant or modify rights, if
> delegated 
> to them by the original author.

Yes, but this has to be done in writing and neither the BSD nor the GPL
license claim to allow this.

> Relicensing and transfer of rights happens all the time.  How do you 
> think most music gets into consumer hands?

Through written agreements to permit this. Neither the BSD nor the GPL
license do. You cannot revoke someone's GPL rights to code you did not
write because they flow directly from the original author to the recipient.

The GPL is quite clear, you do not grant a license to anyone else's code,
the original author does. This is why the GPL does not need to be in writing.

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/