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] [day] [month] [year] [list]
Message-ID: <20070903145053.GX16016@stusta.de>
Date:	Mon, 3 Sep 2007 16:50:53 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Jonathan Gray <jsg@...lin.cx>, Reyk Floeter <reyk@...nbsd.org>
Cc:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: [reyk@...nbsd.org: Re: That whole "Linux stealing our code"
	thing]

On Mon, Sep 03, 2007 at 11:25:42PM +1000, Jonathan Gray wrote:

> This is a lot more relevant than much of the ongoing
> discussion, so perhaps people could take a moment to read it over.
> 
> ----- Forwarded message from Reyk Floeter <reyk@...nbsd.org> -----
> 
> From: Reyk Floeter <reyk@...nbsd.org>
> Date: Mon, 3 Sep 2007 13:23:04 +0200
> To: misc@...nbsd.org
> Subject: Re: That whole "Linux stealing our code" thing
> 
> Hi!
> 
> I just returned from vacation where I was offline for about two weeks.
> So I totally missed the incidence and all the surrounding discussion.
> I'm just digging through many many mails in my inbox from OpenBSD
> users and developers, Linux people, GNU/freesoftware people, misc *BSD
> people, and obviously from some trolls.
> 
> I don't want to restart the discussion but I just want to say and
> repeat a few words:
> 
> - I will not release or agree to release my code under either the GPL
> or any kind of a "dual"-license.

It's your code and it's your choice.

(But note that you contributed to then dual-licenced code in the
 OpenBSD CVS and kept this code dual-licenced. For this code your
 contributions might be assumed dual-licenced.)

> - The ISC-style license must remain including the copyright notice and
> even the warranty term.

Full agreement (for not dual-licenced code).

> - Thanks to the OpenBSD community and especially to Theo de Raadt for
> entering into it and for defending my rights as the author of the
> controversial code.

The email of Theo that was forwarded to linux-kernel [1] centered around 
Theo telling people that picking one licence for Sam's dual-licenced 
code would "break the law".

He would have better made the mistake in Jiri's patch visible (and 
therefore better defended your copyright) if he wouldn't have obscured 
it with these pointless accusations...

> - This is eating our time. Every few weeks I get a new discussion
> about licensing of the atheros driver etc. blah blah. Why can't they
> just accept the license as it is and focus on more important things?
> 
> I will talk to different people to get the latest state and to think
> about the next steps. I don't even know if the issue has been solved
> in the linux tree.
>...

To clarify this myth once again:

The patch that mistakenly changed BSD-only code to GPL has never ever 
been in the Linux tree.

> Thanks!
> reyk

cu
Adrian

[1] http://lkml.org/lkml/2007/9/1/102

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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