linux-kernel - Re: Wasting our Freedom

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]

Date:	Mon, 17 Sep 2007 16:43:18 -0400
From:	Theodore Tso <tytso@....edu>
To:	Claudio Jeker <cjeker@...hard.n-r-g.com>,
	Adrian Bunk <bunk@...nel.org>,
	"Can E. Acar" <can.acar@...-g.com.tr>, misc@...nbsd.org,
	linux-kernel@...r.kernel.org,
	Daniel Hazelton <dhazelton@...er.net>,
	Eben Moglen <moglen@...twarefreedom.org>,
	Lawrence Lessig <lessig_from_web@...ox.com>,
	"Bradley M. Kuhn" <bkuhn@...twarefreedom.org>,
	Matt Norwood <norwood@...twarefreedom.org>
Subject: Re: Wasting our Freedom

On Mon, Sep 17, 2007 at 09:23:41PM +0200, Claudio Jeker wrote:
> Because they put their copyright plus license on code that they barely
> modified. If they would have added substantial work into the OpenHAL code
> and by doing that creating something new I would not say much.

Number 1, some of the Linux wireless developers screwed up earlier
versions.  No denying that, the problems were pointed out during the
patch reviewed problem, AND THEY WERE FIXED.

Number 2, if you take a look at their latest set of changes (which
have still not been accepted), the HAL code is under a pure BSD
license (ath5k_hw.c).  Other portions are dual licensed, but not the
HAL --- if people would only take a look at

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=tree;f=drivers/net/wireless;h=2d6caeba0924c34b9539960b9ab568ab3d193fc8;hb=everything

And yet, the BSD folks seem to continue to nurse the above mantra
(which was true, but quickly corrected) combined with the "and the
Linux folks aren't listening", which is manifestly not true.  We might
not agree with everything you are saying, and we might think you're
being highly hypocritical, but we are listening.

> All the comercial code I have ever seen did not do this stunt of adding a
> new copyright and license to barely modified files. Perhaps the "evil"
> companies have more ethics or better understanding of copyright.

In the original BSD 4.3 code, if I recall correctly, /bin/true was 12
lines of AT&T copyright and the standard "this is proprietary
non-published trade secret" legalease with the standard threats of
bazillions and bazillions of damage due to AT&T's irreparable harm if
the file was ever disclosed....  followed by "exit 0".  :-)

Personally, I find that issues of copyright are much more easily
discussed if people keep a sense of balance and humor.  

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