linux-kernel - Re: GPL weasels and the atheros stink

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:	Sun, 02 Sep 2007 13:34:54 -0400
From:	Michael Tharp <gxti@...tiallystapled.com>
To:	espie@...im.net
CC:	linux-kernel@...r.kernel.org
Subject: Re: GPL weasels and the atheros stink

Marc Espie wrote:
> Let's extend the story a wee little bit. It seems that these days, some
> parts of the opensource community have gotten confident enough that they
> do not need the other part. We all know the situation is already fairly
> disymetric. The GPL is less free than the ISC licence for instance (for
> some definition of free), [...]

It does indeed depend on your definition of free. I, for one, find
BSD/ISC "more free" since it grants rights to any potential user or
contributor, not just those using a compatible license. Others may find
the GPL "more free" since it encourages contributors to give their code
back to the original project, or at least allows the original project to
consume those changes, meaning that the project can benefit from changes
made by a third party and still remain usable by all.

> So, now, it's down to dirty fighting. Absorbing and `relicensing' and 
> evolving code.  Have you all been bitten my RMS paranoia (that leads to
> this `interesting GPLv3) ? Do you intend to keep grabbing BSD code and
> putting it exclusively under the GPL ?

That's the bittersweet side of BSD licensing - others have every right
to take your code and use it for their own projects without having to
give their changes back to you.

> Well, if that's truely the case, I may reconsider my good faith for future
> contributions. Heck, instead of giving away my code under the GPL, I could
> keep my contributions in the form of patches. Ironically, with tools such
> as git, this is no longer as cumbersome as this used to be. So, instead
> of new gcc code sent to the FSF (and given to the FSF), we could explicitly
> keep patches under the ISC licence, and explain loudly why this is so.

Technologically quite easy, yes, and while I'm sure no-one would really
challenge you for doing so. it'd be interesting to know how legal it
would be to distribute an ISC patchset on top of GPL code.

> Nice going, GPL fan-boys...
> --
> 	Marc Espie

-- m. tharp, BSD fanboy, devil's advocate
-
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/