linux-kernel - Re: GPLv3 Position Statement

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: <451B5A59.9040806@garzik.org>
Date:	Thu, 28 Sep 2006 01:15:05 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chase Venters <chase.venters@...entec.com>
CC:	Sergey Panov <sipan@...an.org>, Linus Torvalds <torvalds@...l.org>,
	Patrick McFarland <diablod3@...il.com>,
	Theodore Tso <tytso@....edu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	James Bottomley <James.Bottomley@...eleye.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

Chase Venters wrote:
> I sympathize with Richard on his avoidance of "open-source". I don't 
> necessarily take the same view, but I understand that his big concern is that 
> the message he feels is important will be lost. I also think some of the 
> things I've heard from the "open-source" side are too extreme - take, for 
> instance, ESR's idea that we don't need the GPL license at all. That sounds 
> like a nice world he's living in, but I'm not sure we're all on the same 
> planet yet.

ESR is a nutcase too.


> The final GPLv3 may indeed go too far for many open-source supporters. But 
> then again, it is the FSF's license, and it should at least not surprise 
> anyone if they are more concerned with the ideals of the license rather than 
> current market realities. Market conditions change; ideals generally don't.

As long as you can admit that FSF is divorced from reality...

	Jeff


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