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: <orodjib9b6.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Thu, 14 Jun 2007 16:55:09 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Diego Calleja <diegocg@...il.com>, Adrian Bunk <bunk@...sta.de>,
	Valdis.Kletnieks@...edu, Daniel Hazelton <dhazelton@...er.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 14, 2007, Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, 14 Jun 2007, Diego Calleja wrote:

>> And the FSF is trying to control the design and licensing of
>> hardware throught the influence of their software.

It's not.  It's only working to ensure recipients of the Free Software
can modify and share the software.

>> What the FSF is trying to do is EVIL.

> I wouldn't go that far (although, in the heat of the moment I probably 
> _have_ gone that far. Oops ;).

:-)

> I literally think that the GPLv2 has worked so well exactly because you 
> can strip it of its high-falutin' morality and the FSF Kool-Aid, and just 
> see it as a "tit-for-tat" license. It allows everybody to see that the 
> work they put in (into the _software_) is protected, and people cannot 
> make improved versions of that software and distribute those improved 
> versions without giving you the right back to use those improvements (to 
> the _software_).

Can you explain to me how it is that the Tivoization provisions (the
only objection you have to GPLv3) conflict with this?

(nevermind our disagreement as to whether "tit-for-tat" applies to
 either GPLv2 or GPLv3)

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
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