From mboxrd@z Thu Jan  1 00:00:00 1970
Reply-To: kernel-hardening@lists.openwall.com
MIME-Version: 1.0
Sender: keescook@google.com
In-Reply-To: <20160119222052.4c093972b55873bd61a416ae@gmail.com>
References: <20151106235545.97d0e86a5f1f80c98e0e9de6@gmail.com>
	<CAGXu5jL5JV2WS2GVuL16N82DYGVqshveOfWs=iTzH+1XeuSiaA@mail.gmail.com>
	<20160119222052.4c093972b55873bd61a416ae@gmail.com>
Date: Tue, 19 Jan 2016 15:08:04 -0800
Message-ID: <CAGXu5jKAxk+7iRvB1AxETjv6_QBCTHOCn0LyLXtKeB=qoRUbJQ@mail.gmail.com>
From: Kees Cook <keescook@chromium.org>
Content-Type: text/plain; charset=UTF-8
Subject: [kernel-hardening] Re: Proposal for kernel self protection features
To: Emese Revfy <re.emese@gmail.com>
Cc: "kernel-hardening@lists.openwall.com" <kernel-hardening@lists.openwall.com>, "pageexec@freemail.hu" <pageexec@freemail.hu>, "spender@grsecurity.net" <spender@grsecurity.net>
List-ID: <kernel-hardening.lists.openwall.com>

On Tue, Jan 19, 2016 at 1:20 PM, Emese Revfy <re.emese@gmail.com> wrote:
>
>> Can you give a status update on the constify plugin work? I'm curious
>> to hear what your plans are.
>
> Hi,
>
> I'll begin with the gcc plugin infrastructure from February on.
> When I'm done with it I'll continue to work on the following plugins
> (I'm not sure of the order maybe I can work in parallel on them):
> 1. initify
> 2. structleak
> 3. latent_entropy
> 4. constify

Sounds great, thanks!

-Kees

-- 
Kees Cook
Chrome OS & Brillo Security