[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151107225810.b5f37120449d0957e3e29d72@gmail.com>
Date: Sat, 7 Nov 2015 22:58:10 +0100
From: Emese Revfy <re.emese@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Josh Triplett <josh@...htriplett.org>, Kees Cook
<keescook@...omium.org>, "kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>, PaX Team <pageexec@...email.hu>,
Brad Spengler <spender@...ecurity.net>, Theodore Tso <tytso@...gle.com>
Subject: Re: Proposal for kernel self protection features
> > 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?
>
> That would be nice for the constanfy mode as well, especially as some
> people aren't using gcc to build the kernel anymore, so it would be good
> to mark these "for real" in the .c code wherever possible to allow other
> compilers to take advantage of the plugin indirectly.
Yes, I can do it of course. There can be two kernel config options:
* warning (dry run) mode: the plugin just prints out the warnings
* constify: do the constification automatically
--
Emese
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.
