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: <Pine.LNX.4.64.0709021416130.6181@condmat1.ciencias.uniovi.es>
Date:	Sun, 02 Sep 2007 14:28:28 +0200 (CEST)
From:	Igor Sobrado <igor@...dmat1.ciencias.uniovi.es>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"Constantine A. Murenin" <mureninc@...il.com>,
	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	Jiri Slaby <jirislaby@...il.com>
Subject: Re: Fwd: That whole "Linux stealing our code" thing

On Sun, 2 Sep 2007, Adrian Bunk wrote:
> On Sun, Sep 02, 2007 at 01:20:27PM +0200, Igor Sobrado wrote:
>> Reyk code was never dual licensed!  His code is under truly free licensing
>> terms (BSD).
>
> Jiri's patch touched both files containing BSD-only code by Reyk and
> code Reyk contributed to leaving the file dual licenced.

Ok.

> You mixed two completely different things in your email:
>
> 1. Jiri's patch (that was never merged into Linux) not only removed the
>   BSD header from dual licenced files but also from not dual licenced
>   files.
>
> 2. Theo accused Alan that telling people that it was OK to choose one
>   licence for dual licenced code was "advising people to break the law".
>
> Jiri's patch was legally not OK regarding 1. - there's no discussion
> regarding this.
>
> The point 2 is what the email of Theo that was forwarded to linux-kernel
> is about and what the discussion is about. That's quite a rude action
> by Theo unless he's able to prove that this accusation is correct.

When code is multi-licensed it must be distributed under *all* these 
licensing terms concurrently.  It is easy to understand.  Removing (or 
changing) the conditions that apply to the program from the source code 
and documentation *without* an authorization from all the author(s) is 
illegal.

So, a multi-licensed file remains multi-licensed except when all authors 
agree about a change in the licensing terms.  And it is clear on the BSD 
license that a modification of the distribution terms is illegal.  It is 
the first clause on the BSD license:

  * 1. Redistributions of source code must retain the above copyright
  *    notice, this list of conditions and the following disclaimer,
  *    without modification.

So, removing (or changing) the list of conditions on the BSD license is 
not allowed.

Igor.
-
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