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: <46EE311F.5040107@aitel.hist.no>
Date:	Mon, 17 Sep 2007 09:47:43 +0200
From:	Helge Hafting <helge.hafting@...el.hist.no>
To:	Theodore Tso <tytso@....edu>, 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

Jacob Meuser wrote:
> On Sun, Sep 16, 2007 at 05:12:08PM -0400, Theodore Tso wrote:
>
>   
>> reimplement them.  Why don't you go and try asking NetApp for sources
>> to WAFL, and claim that they have "moral" duty to give the code back,
>> and see how quickly you get laughed out of the office?
>>     
>
> which is _exactly_ what you guys are doing.
>
> so the linux community is morally equivilent to a corporation?
>
> that's what it sounds like you are all legally satisfied with.
>   
A difference between linux and corporations: Linux actually
gives changed source code back - just not with a BSD licence on it.
So you can at least see what the linux community did, and do
the same. Although not by direct copying.

But why complain when the linux community do what the
BSD licence lets them?  If you think the linux community
is abusing a loophole in the licence, why don't you just close
the hole? For example, require that changes made to your
code when used in the linux kernel must be made
available under a BSD licence also. Still possible to use
the code anywhere, but with a guarantee of getting stuff back.

Your problem seems to be with the BSD licence,
and the power to alter that licence lies in the BSD community.

Helge Hafting









-
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