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  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:	Sat, 1 Sep 2007 21:42:54 -0400
From:	"Luis R. Rodriguez" <>
To:	"Constantine A. Murenin" <>
Cc:	"Jeff Garzik" <>,
	"Jason Dixon" <>,,,,,
Subject: Re: That whole "Linux stealing our code" thing

On 9/1/07, Constantine A. Murenin <> wrote:
> On 01/09/07, Jeff Garzik <> wrote:
> > Jason Dixon wrote:
> > > Once the grantor (Reyk) releases his code under that license, it must
> > > remain.  You are free to derive work and redistribute under your
> > > license, but the original copyright and license permission remains
> > > intact.  Many other entities (Microsoft, Apple, Sun, etc) have used BSD
> > > code and have no problem understanding this.  Why is this so difficult
> > > for the Linux brain share to absorb?
> >
> > Why is it so difficult to understand dual licensing?
> Maybe because Reyk's code was never dual-licensed?

We asked SFLC to work with us to make sure that everyone's copyrights
were respected in the right places, and that the licenses various developers
wanted for their copyrights were implemented correctly.  The patch I sent
implements SFLC's suggestions in that regard.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists