linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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: <1182144137.21797.1449.camel@localhost.localdomain>
Date:	Mon, 18 Jun 2007 13:22:17 +0800
From:	Tim Post <tim.post@...kinetics.net>
To:	david@...g.hm
Cc:	Alexandre Oliva <aoliva@...hat.com>,
	Bernd Petrovitsch <bernd@...mix.at>,
	Gabor Czigola <czigola@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Sun, 2007-06-17 at 14:13 -0700, david@...g.hm wrote:
> you argue that it is evil for tivo to produce a pice of hardware that they 
> can modify and the user can't
> 
> but you then argue that it's a good thing for the FSF to produce a license 
> that they can modify and others can't

They can't modify the license that you used. They can make a new license
which you may optionally use at your discretion.

Once you release the code under the GPL(x), that is it. The only person
who can change that is you or perhaps some bizarre court order. But it
would still be you changing it, even if your hand was forced to do so.

Your copyright is your signing mechanism. Once you do it, its a done
deed. That is the whole reason Linus chose GPL2 to begin with, I
believe :)

You and _only_ you are the one. Its like a biometric lock.

Best,
--Tim

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