From: David Brown <david.brown@linaro.org>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Self Introduction
Date: Wed, 9 Dec 2015 16:26:51 -0800 [thread overview]
Message-ID: <20151210002651.GC99337@davidb.org> (raw)
In-Reply-To: <CAGXu5jLLXK3N6pbZOie5uj276x=dtc_tuTz312rnhF8yrmxHYQ@mail.gmail.com>
On Wed, Dec 09, 2015 at 04:14:20PM -0800, Kees Cook wrote:
>Great! It might be valuable to read through this mailing lists's
>threads over the last month. We discuss a few of the features and some
>work has been started.
Reading through stuff now. Looks like the list got quite a boost in
November.
>> I suspect part of the challenge is going to be clearly describing the
>> various features along with specific examples of already-discovered
>> exploits that the feature would have mitigated.
>
>Yes indeed. :) That's why I've arranged the wiki the way I did:
>classes and methods first, with potential solutions listed under them.
>We want to start with problem descriptions and work from actual
>exploits when possible.
>
>This is why the recent x86 VDSO attack was very timely: it
>demonstrates cleanly why we want __ro_after_init (née __read_only) in
>upstream. (As well as the constification plugin.)
Which also seems like this will be quite useful on ARM as well. Do
you know any efforts to do this?
>> Most recently, I backported ARM PAN support to the Linaro stable
>> kernels (3.18 and 4.1).
>
>Excellent! Yes, I did a port to Brillo's v4.1 tree as well. It's very
>nice to have a UDEREF-like feature on arm. It's too bad this doesn't
>exist for Intel yet, but I'm hoping they'll step up.
>
>For 3.18, is this the right place to be looking?
>https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=shortlog;h=refs/heads/linux-linaro-lsk-v3.18
It will be once it gets through testing.
https://git.linaro.org/kernel/linux-linaro-stable.git/shortlog/refs/heads/v3.18/topic/PAN
to peek before then. There's also
https://git.linaro.org/kernel/linux-linaro-stable.git/shortlog/refs/heads/v4.1/topic/PAN
for the 4.1 tree.
Should I CC kernel-hardening when sending patches for the Linaro
stable kernels?
>I'd love to see CONFIG_CPU_SW_DOMAIN_PAN into the AOSP 3.18 android kernel too.
I'll put this on my list to investigate. Sadly, it looks like there
is a bit of a window of ARM CPUs where neither solution will work;
Basically the pre V8.1 64-bit.
In fact, I don't have any hardware yet that supports PAN. I've done
all of the testing in emulation.
David
next prev parent reply other threads:[~2015-12-10 0:26 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 17:21 [kernel-hardening] Self Introduction David Brown
2015-12-09 22:19 ` Kees Cook
2015-12-10 0:00 ` David Brown
2015-12-10 0:14 ` Kees Cook
2015-12-10 0:26 ` David Brown [this message]
2015-12-10 0:41 ` Kees Cook
2015-12-10 17:14 ` Stephen Smalley
2015-12-10 17:49 ` Kees Cook
2015-12-10 17:55 ` Daniel Micay
2015-12-10 18:42 ` Kees Cook
2015-12-10 19:07 ` Daniel Micay
2015-12-10 19:23 ` Kees Cook
2015-12-10 19:38 ` Schaufler, Casey
2015-12-10 19:45 ` Kees Cook
2015-12-11 17:54 ` Valdis.Kletnieks
2015-12-11 18:44 ` Kees Cook
2015-12-12 11:40 ` Heiko Carstens
2015-12-10 22:38 ` PaX Team
2015-12-10 23:04 ` Daniel Micay
2015-12-10 18:42 ` Catalin Marinas
2015-12-10 18:47 ` Kees Cook
2015-12-10 23:52 ` Kees Cook
2015-12-11 1:04 ` David Brown
2016-01-11 18:33 ` David Brown
2016-01-12 19:31 ` Kees Cook
2016-01-13 11:29 ` Catalin Marinas
2016-01-13 11:31 ` Catalin Marinas
2016-01-14 1:04 ` Ben Hutchings
2016-01-14 11:11 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2016-10-09 12:34 [kernel-hardening] self introduction Colin Vidal
2016-10-09 14:04 ` David Windsor
2016-10-09 19:09 ` Colin Vidal
2016-10-09 19:37 ` Jann Horn
2016-10-10 6:02 ` Reshetova, Elena
2016-10-10 16:01 ` Colin Vidal
2016-10-10 17:01 ` Reshetova, Elena
2016-10-10 21:05 ` Kees Cook
2016-10-12 3:19 ` Gengjia Chen
2016-10-12 22:31 ` Kees Cook
2016-10-13 11:14 ` Gengjia Chen
2016-10-13 18:50 ` Kees Cook
2016-10-17 11:57 ` Gengjia Chen
2016-10-17 20:15 ` Kees Cook
2016-10-18 11:52 ` Gengjia Chen
2016-10-18 21:21 ` Kees Cook
2016-10-12 8:25 ` Colin Vidal
2016-10-12 22:35 ` Kees Cook
2016-10-13 13:54 ` Reshetova, Elena
2016-10-13 18:53 ` Kees Cook
2016-10-13 19:26 ` Hans Liljestrand
2016-10-10 20:57 ` Kees Cook
2016-10-12 8:27 ` Colin Vidal
2016-10-12 22:40 ` Kees Cook
2016-10-14 18:32 ` Andy Lutomirski
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=20151210002651.GC99337@davidb.org \
--to=david.brown@linaro.org \
--cc=kernel-hardening@lists.openwall.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.