linux-kernel - Re: Fwd: That whole "Linux stealing our code" thing

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: <20070902134612.28a88761@the-village.bc.nu>
Date:	Sun, 2 Sep 2007 13:46:12 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Igor Sobrado <igor@...dmat1.ciencias.uniovi.es>
Cc:	Adrian Bunk <bunk@...nel.org>,
	"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

> 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 

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.

A multi-licensed work (note work not file - don't assume a file is a
boundary of a work) which conveys the choice of licence (as some bits of
ath5k did) allows a receiving party to choose the licence it wishes.
Failing that OpenBSD would have turned itself GPL by adding that file as
according to your argument "it must be distributed under *all* these
licensing terms concurrently".

Alan
-
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/