From: Kees Cook <keescook@chromium.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Paul Moore <paul@paul-moore.com>,
SELinux <selinux@vger.kernel.org>,
Jeffrey Vander Stoep <jeffv@google.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
Connor Kuehl <cipkuehl@gmail.com>,
Dan Aloni <daloni@magicleap.com>
Subject: Re: Does anyone use RANDSTRUCT?
Date: Fri, 13 Dec 2019 10:05:50 -0800 [thread overview]
Message-ID: <201912130943.A301DBF@keescook> (raw)
In-Reply-To: <bf727420-b7bd-d3e9-a597-812922ba20a3@tycho.nsa.gov>
On Fri, Dec 13, 2019 at 10:40:54AM -0500, Stephen Smalley wrote:
> See $(subject). If yes, there are some obvious candidates among the SELinux
> data structures for randomized layouts to avoid fixed locations for
> enforcing, initialized, etc. If not, then no point in pursuing it. Doesn't
> look like Fedora enables it, probably because they'd have to publish the
> random seeds anyway for third party kernel modules. But maybe it would be
> useful for some distros/users? ChromeOS? Android?
It is used by "in-house" kernel builders who optimize for high security
above all other things (I've talked to a few of them over the years
when finding out what defenses they've wanted). I've also seen Huawai
Android patches that seem to indicate they're using it as well, but I
haven't been able to determine if any released devices are shipping with
it enabled. I've also had several people ask after the Clang randstruct
port, which is ongoing[1] by a couple people (added to CC).
I think it would be very handy to add some more markings to sensitive
data structures. Please send patches!
-Kees
[1] https://reviews.llvm.org/D59254
https://github.com/da-x/llvm-project/commits/clang-r365631c-randstruct
https://github.com/da-x/linux/commits/android-4.19-randstruct
https://github.com/connorkuehl/llvm-project/commits/randstruct
https://github.com/connorkuehl/llvm-project/pull/21
--
Kees Cook
next prev parent reply other threads:[~2019-12-13 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 15:40 Does anyone use RANDSTRUCT? Stephen Smalley
[not found] ` <CAOSEQ1qhxdA+JW4M6rOqjzTuMXu2hr0jxRt9NfkuEcWW7-_BEQ@mail.gmail.com>
2019-12-13 15:53 ` Stephen Smalley
2019-12-13 18:05 ` Kees Cook [this message]
2019-12-13 18:36 ` Stephen Smalley
2019-12-13 22:39 ` Dan Aloni
2019-12-15 0:33 ` Connor Kuehl
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=201912130943.A301DBF@keescook \
--to=keescook@chromium.org \
--cc=cipkuehl@gmail.com \
--cc=daloni@magicleap.com \
--cc=jeffv@google.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
/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.