linux-kernel - Re: Replacing GNU

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140402024633.GB29944@thunk.org>
Date:	Tue, 1 Apr 2014 22:46:33 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Andrew Stephenson <aste9@...oud.com>
Cc:	David Lang <david@...g.hm>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Replacing GNU

On Wed, Apr 02, 2014 at 01:03:13PM +1100, Andrew Stephenson wrote:
> Ah, so there is a Free Software camp and an Open Source camp within
> the Linux Kernel Mailing List.

There is a strong consensus that the Linux kernel should remain GPLv2,
and many senior kernel developers (including Linus) have an extremely
strong dislike of the GPLv3's anti-Tivo clauses.  I suspect many of us
regret that license incompatibilities caused by some code being
licensed under GPLv2 only, and some code being licensed under GPLv3,
but that's an issue that you need to talk to the FSF about.

As far as the kernel is concerned, it doesn't use the gcc runtime
library, so issues about GPLv3 are simply simply not a major concern
for most linux kernel developers.

Questions about what the implications are of GPLv3 licensed code in
userspace really are out of scope of the LKML mailing list.  If you
care about such things, I suggest you talk to your lawyers.

Cheers,

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