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: <20070902113638.78fbd202@the-village.bc.nu>
Date:	Sun, 2 Sep 2007 11:36:38 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Constantine A. Murenin" <mureninc@...il.com>
Cc:	"Adrian Bunk" <bunk@...nel.org>, "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

> - If you receive ISC or BSD licensed code, you may not delete the
>  license.  Same principle, since the notice says so.  It's the law.
>  Really.

You can shout this all you like but you would be wrong. You can remove
the licence if you have permission to do so. For the ath c files there
was permission to do so.

> My understanding is that with dual-licensed code, you choose to comply
> with all of the terms of either licence. However, you cannot simply
> remove either of these licences from the code, unless you specifically
> receive such right from the copyright holder (remember, with the
> copyright law, unless the rights are specifically given, they are
> retained). This is what Theo was trying to educate the community on. I
> don't see anything unethical in explaining the legal issues.

Your understanding isn't quite right. One of many things you may get with
dual licensed code is the right to pick a licence from several choices,
you may also get the right to remove some choices from the recipient.

A work that combines GPL and BSD licensed material is not the same as a
work which says I may choose between two licences. If both licences must
always apply (which is a perfectly possible condition to put in a
licence) then putting such a "both" GPL/BSD licence piece of code into
OpenBSD would require any OpenBSD distributed containing it was GPL
licenced when conveyed, which I am *very* sure is not the intent.

Thus what you appear to be doing by putting the ath5k C code in OpenBSD is
conveying it under the BSD licence (making a choice between the two
offered) and conveying a right for parties down the chain to convey it
under one of the licences only.

And as we've already established the header files are quite different.

Doesn't mean its not somewhat rude but illegal and rude are two very
different things.

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