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: <7579f7fb0709021123p7088ec41m5b688f527ba46d13@mail.gmail.com>
Date:	Sun, 2 Sep 2007 11:23:11 -0700
From:	"Matthew Jacob" <lydianconcepts@...il.com>
To:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Fwd: That whole "Linux stealing our code" thing

This has been pretty interesting for me to watch as I distribute my
isp driver under a dual license (at least the portions of it which are
common with the *BSD and Solaris ports)  that is almost identical to
Sam's verbiage.

I'll admit that I hadn't thought about whether redistribution included
the ability to modify the header (and thus the text of the licensing
as I had written) or not. On balance I'd say I believe that the
arguments for, on redistribution, picking one or the other license
makes sense and honored my general intent.

This allows people who modify the code (and presumably improve it) a
"chef's choice" based on where they're serving the meal.

IANAL, but I believe that none of this keeps me from continuing to put
a dual license on stuff I leave up for distribution, or changing that
to restricting the code to Martian Triathalon winners or what have
you.
-
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/