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  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, 2 Sep 2007 19:21:15 +0100
From:	Al Viro <>
To:	Igor Sobrado <>
Cc:	Alan Cox <>, Adrian Bunk <>,
	"Constantine A. Murenin" <>,
	Jeff Garzik <>,,,,
	Jiri Slaby <>
Subject: Re: Fwd: That whole "Linux stealing our code" thing

On Sun, Sep 02, 2007 at 03:00:46PM +0200, Igor Sobrado wrote:
> >Not strictly true. They can either agree to a change and issue one or
> >they can convey to other parties the right to change the terms. The GPL
> >for example does this for version selection.
> So, under a dual-licensed BSD/GPL code the latter license allows a 
> developer to remove the GPL license itself and release a single-licensed 
> BSD code if other parties want to do it?

Exactly.  That's what dual-licensing is.

This is no different from the fact that we have some drivers that are
GPLv2/BSD licensed. Within the kernel, they are GPLv2. But on their own, 
you can choose to use them under the BSD license, make your changes to
them, and release them commercially.
And correct - I cannot (and neither can anybody else) then accept those
*non*GPLv2 changes back.
[end quote]

That's from Linus and quite recently.

FWIW, it's damn hard to codify "... and changes to this code should not
change the situation".  It's certainly a very good policy and in this
case it's the only sane policy.

Actually, normally I *do* have such a trust. It's why I have no problem
with drivers that are dual-GPL/BSD, and in fact, I've told people that I
don't want them to turn them into GPL-only, because that is simply not   
[end quote]

Same posting from Linus.  And that's much more relevant to shooting the patch
in question down (and IMO it ought to be shot down) than references to
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists