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]
Message-ID: <f34ca13c0709012209x64c282b9o1fd0cb7d08690247@mail.gmail.com>
Date:	Sun, 2 Sep 2007 01:09:18 -0400
From:	"Constantine A. Murenin" <mureninc@...il.com>
To:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>
Cc:	"Adrian Bunk" <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>, jirislaby@...il.com,
	"Nick Kossifidis" <mickflemm@...il.com>
Subject: Re: That whole "Linux stealing our code" thing

On 01/09/07, Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:
> On Sun, 02 Sep 2007 03:55:37 +0200, Adrian Bunk said:
>
> > Jiri's patch would have wrongly not only removed the BSD statement from
> > dual licenced files but also from not dual licenced files.
> >
> > This was a mistake in this patch (that was never merged into the tree)
> > neither Jiri nor Alan noticed.
>
> You know, we *could* have solved this a *hell* of a lot easier if people quit
> flaming about it, and we did something *productive* instead.
>
> Like submit a corrected patch. :)

Dear Valdis,

The idea here is that no patching was needed in the first place --
most of the files are/were BSD-licensed, because they were forked from
OpenBSD.

It is beneficial for the atmosphere of both projects to keep the
licence compatible. If Linux tries to GPL future modifications to
Reyk's code, then OpenBSD would not be able to take back the changes.
But this would not be the case if all modifications to Reyk's code are
continued to be BSD-licensed. This is what this whole issue is about.

My understanding, is that Nick Kossifidis never had a problem with
licensing his changes with a BSD-license, although Jiri Slaby always
used GPLv2.

With the last patch posted by Luis [0], Jiri actually recalled his
original patch and relicensed all of his GPLv2 work under BSD (!);
however, at the very same time, Nick changed his mind, and decided to
relicense his BSD code under GPLv2 (!). (Surprise! Yes, it appears
that both Nick and Jiri decided to switch their licensing positions,
and mutually relicense their work under each other's respective
licence. :) Is everyone ready going to go back and forth now? Does
this whole story still makes any sense to you? :)

I hope that both Nick Kossifidis and Jiri Slaby can agree on licensing
their HAL code with a BSD licence, so that the code remains
licence-compatible with OpenBSD. If there are any unresolved licensing
questions, I personally would be more than happy to answer any such
questions as much as I can, and yes -- I am not a lawyer. :)

Nick, Jiri -- since much of the work on OpenHAL is based on Reyk's
HAL, could you please be so kind as to both agree to licence you
changes in OpenHAL with the same licence as Reyk does in OpenBSD's
ath(4) HAL? This step will be very welcome in the OpenBSD community at
large.

Best regards,
Constantine.

[0] http://marc.info/?l=linux-wireless&m=118857712529898&w=2
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ