[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151107002508.GA2605@cloud>
Date: Fri, 6 Nov 2015 16:25:08 -0800
From: Josh Triplett <josh@...htriplett.org>
To: Kees Cook <keescook@...omium.org>
Cc: Emese Revfy <re.emese@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
PaX Team <pageexec@...email.hu>,
Brad Spengler <spender@...ecurity.net>,
Greg KH <gregkh@...uxfoundation.org>,
Theodore Tso <tytso@...gle.com>
Subject: Re: Proposal for kernel self protection features
On Fri, Nov 06, 2015 at 03:30:39PM -0800, Kees Cook wrote:
> On Fri, Nov 6, 2015 at 2:55 PM, Emese Revfy <re.emese@...il.com> 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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
