linux-kernel - Re: Wrapping EXPORT_SYMBOL_GPL symbols and re-exporting the wrappers with EXPORT

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:	Tue, 2 Jul 2013 09:57:08 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Bjørn Mork <bjorn@...k.no>,
	LKML <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: Wrapping EXPORT_SYMBOL_GPL symbols and re-exporting the wrappers
 with EXPORT_SYMBOL

On Mon, Jul 1, 2013 at 11:38 PM, Borislav Petkov <bp@...en8.de> wrote:
> On Mon, Jul 01, 2013 at 03:32:27PM +0200, Bjørn Mork wrote:
>> I just got a new wireless router and stumbled across an odd set of
>> out-of-tree modules, where two GPL licensed modules were used by a third
>> proprietary licensed one.
>>
>> The nice router vendor sent me the GPL'd source code, and as expected
>> the GPL modules are little more than wrappers working around the
>> EXPORT_SYMBOL_GPL restrictions.  Here's a complete example of one of
>> them:
>
> I'm wondering if we could fail building modules which do EXPORT_SYMBOL.

Then vendors will do a s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL/g on the kernel.
Recently I've identified such a case.

Bjørn, please post this on legal@...ts.gpl-violations.org too.

--
Thanks,
//richard
--
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/