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]

Message-ID: <20130702081754.GA4535@pd.tnic>
Date:	Tue, 2 Jul 2013 10:17:54 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
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 Tue, Jul 02, 2013 at 09:57:08AM +0200, richard -rw- weinberger wrote:
> Then vendors will do a s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL/g on the kernel.

Huh, "fail building if a module does EXPORT_SYMBOL"...

> Recently I've identified such a case.

Regardless, there's not really a whole lot we can do technically as long
as they go and change the kernel. The EXPORT_SYMBOL_GPL thing protects
only against separately distributed modules but if you deliver the whole
kernel, you can do whatever you want. :-\

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/