From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Date: Fri, 6 Nov 2015 16:25:08 -0800 From: Josh Triplett Message-ID: <20151107002508.GA2605@cloud> References: <20151106235545.97d0e86a5f1f80c98e0e9de6@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [kernel-hardening] Re: Proposal for kernel self protection features To: Kees Cook Cc: Emese Revfy , "kernel-hardening@lists.openwall.com" , PaX Team , Brad Spengler , Greg KH , Theodore Tso List-ID: On Fri, Nov 06, 2015 at 03:30:39PM -0800, Kees Cook wrote: > On Fri, Nov 6, 2015 at 2:55 PM, Emese Revfy wrote: > > * initify: This plugin isn't security related either. > > It moves string constants (__func__ and function string arguments > > marked by the nocapture attribute) only referenced in > > __init/__exit functions to __initconst/__exitconst sections. > > It reduces memory usage (many kB), I think it may be important for > > embedded systems. > > I bet the Tinification project ( https://tiny.wiki.kernel.org/ ) would > be interested in this! (CCing Josh for thoughts.) I'd be quite interested. Could the plugin operate in a mode where it emits warnings to add such annotations explicitly in the code, rather than just automatically moving the data? - Josh Triplett