From: Kees Cook <keescook@chromium.org>
To: Laura Abbott <labbott@redhat.com>
Cc: P J P <ppandit@redhat.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Florian Weimer <fweimer@redhat.com>,
P J P <pjp@fedoraproject.org>
Subject: Re: [PATCH 1/1] Add an option to build kernel with -finit-local-vars
Date: Tue, 27 Feb 2018 11:33:34 -0800 [thread overview]
Message-ID: <CAGXu5j+_biDq6xzgB0mAEm159mFc5fABfqOT4-Yew9t-YdNuvg@mail.gmail.com> (raw)
In-Reply-To: <14a4ef2b-1a32-2781-80db-ee850e25f318@redhat.com>
On Tue, Feb 27, 2018 at 11:22 AM, Laura Abbott <labbott@redhat.com> wrote:
> On 02/27/2018 03:15 AM, P J P wrote:
>> Add a configuration option to build kernel with -finit-local-vars
>> compiler option.[*] It'll zero initialize the automatic kernel
>> function variables, thus helping to reduce kernel information
>> leakage issues.
>
> I think this would make the existing structleak plugin
> (scripts/gcc-plugins/structleak_plugin.c) obsolete. This isn't
> a bad thing but we'd need to figure out a deprecation strategy.
It would be nice to make it obsolete, but I don't think that'll happen
right away. We still have issues with structure padding,
passed-by-reference init, and possibly performance. I wouldn't want to
rule anything out until we can have both more complete coverage and
better benchmarks (e.g. this is wipe-before, not wipe-after, so there
may be cache effects, etc).
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2018-02-27 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:15 [PATCH 0/1] Zero initialise kernel stack variables P J P
2018-02-27 11:15 ` [PATCH 1/1] Add an option to build kernel with -finit-local-vars P J P
2018-02-27 19:22 ` Laura Abbott
2018-02-27 19:33 ` Kees Cook [this message]
2018-02-28 5:49 ` P J P
2018-02-27 19:28 ` [PATCH 0/1] Zero initialise kernel stack variables Kees Cook
2018-02-27 23:26 ` Laura Abbott
2018-02-27 23:38 ` Kees Cook
2018-02-28 6:22 ` P J P
2018-02-28 8:25 ` Florian Weimer
2018-02-28 6:04 ` P J P
2018-03-02 19:52 ` Nick Kralevich
2018-03-02 21:01 ` Casey Schaufler
2018-03-05 20:42 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGXu5j+_biDq6xzgB0mAEm159mFc5fABfqOT4-Yew9t-YdNuvg@mail.gmail.com \
--to=keescook@chromium.org \
--cc=fweimer@redhat.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.