linux-kernel - Re: GPL version 4

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]

Date:	Thu, 17 Jul 2008 08:21:28 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	"Morton Harrow" <mharrow@...uxmail.org>
Cc:	"Miod Vallat" <miod@...ine.fr>, licensing@....org,
	linux-kernel@...r.kernel.org, rms@....org,
	claire.newman@...onical.com, announce@...europe.org,
	misc@...nbsd.org, ubuntu-users@...ts.ubuntu.com,
	fedora-list@...hat.com, netbsd-users@...bsd.org,
	freebsd-questions@...ebsd.org
Subject: Re: GPL version 4

On Jul 16, 2008, "Morton Harrow" <mharrow@...uxmail.org> wrote:

> I see with pain in my heart that the GPLv3 doesn't actually give the
> users of GPLv3 software the liberty and freedom the FSF has been
> fighting for. Instead they are forced to play by the strict set of
> terms the GPLv3 provides.

> For example, as a liberated computer user, I might like to incorporate
> a high quality piece of GPLv3 software in a commercial product,

You can do that.  There are lots of commercial products containing
GPLv3 software out there.

> which for bussiness strategic reasons happens to be closed source software.
> But the GPLv3 denies my claim for this freedom to do this.

You are mistaken in several levels.

1. Disrespecting others' freedoms is not a matter of freedom, it's a
matter of power.

2. Nothing in the GPL prevents you from doing any of this.  If there
is something that prevents you from doing this, it's copyright law.
You won't find prohibitions in the GPL.

3. If you're unable to combine third-party GPL-incompatible software
with GPL software, it's because the third party prevented you from
doing this, and you accepted it.  Don't blame the GPL for your
acceptance of such terms.

4. If you decide to not release your own code under the GPL, even
though this stops you from releasing the program you wrote with help
from other authors who chose the GPL, that's your decision.  Don't
blame the GPL for the consequences of your own decisions.

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