linux-kernel - Re: [PATCH 05/14] KDB: add more exports for supporting KDB modules

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>] [day] [month] [year] [list]

Message-ID: <20130313145302.GA23308@mail.lurndal.org>
Date:	Wed, 13 Mar 2013 07:53:02 -0700
From:	Scott Lurndal <scott@...ndal.org>
To:	travis@....com
Cc:	jason.wessel@...driver.com, linux-kernel@...r.kernel.org,
	ebiederm@...ssion.com
Subject: Re: [PATCH 05/14] KDB: add more exports for supporting KDB modules

> Looking back at the KDB sources originally posted on oss.sgi.com I
> did not see any restrictions on the use of KDB.  How/why was that
> restriction granted and by whom?  Was SGI, the original copyright
> owner of KDB, asked or even informed of that decision?  I'm not
> trying to be a lawyer here, but someone decided (perhaps wrongly)
> that KDB should only be used by GPL modules.

At the time that I wrote that original KDB code at SGI, there was no
intent to make it only usable by GPL modules.  If anything, it was intended
to be more in the BSD-style (anyone can use it any way they like with
attribution) than the GPLv3-style (use it our way, or else).

But then, EXPORT_SYMBOL_GPL didn't exist then.  And I think its existence
is silliness on the part of several hard-core developers.

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