From: Mark Rutland <mark.rutland@arm.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Jann Horn <jann@thejh.net>
Subject: Re: [Ksummit-discuss] [nominations] kernel hardening / self-protection / whatever
Date: Mon, 1 Aug 2016 10:34:27 +0100 [thread overview]
Message-ID: <20160801093417.GA11119@leverpostej> (raw)
In-Reply-To: <3aa8df3e-3705-9fd5-640c-37c0be2af561@imgtec.com>
On Sun, Jul 31, 2016 at 10:55:29AM +0100, Paul Burton wrote:
> It would be interesting to hear from people focused on security what
> their requirements, current & coming soon, from arch code are.
I'd be interested in this, and I think it would also be worth having:
- Ard Biesheuvel
- Laura Abbott
Who have both done work on various protection improvements for arm/arm64
(e.g. DEBUG_RODATA & KASLR), and generic infrastructure pieces (e.g.
LKDTM).
Thanks,
Mark.
prev parent reply other threads:[~2016-08-01 9:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 4:28 [Ksummit-discuss] [TOPIC] kernel hardening / self-protection / whatever Andy Lutomirski
2016-07-11 13:05 ` Rafael J. Wysocki
2016-07-11 16:30 ` Eric W. Biederman
2016-07-11 17:57 ` Kees Cook
2016-07-12 16:40 ` Eric W. Biederman
2016-07-21 15:54 ` Mark Rutland
2016-07-11 17:33 ` Jann Horn
2016-07-19 15:40 ` Eric W. Biederman
2016-07-20 2:14 ` Andy Lutomirski
2016-07-20 2:14 ` Eric W. Biederman
2016-07-20 6:42 ` Herbert Xu
2016-07-21 17:03 ` Eric W. Biederman
2016-07-11 17:53 ` Kees Cook
2016-07-11 18:07 ` Josh Triplett
2016-07-11 18:59 ` Kees Cook
2016-07-31 9:55 ` Paul Burton
2016-07-31 22:04 ` Kees Cook
2016-08-01 10:47 ` Mark Rutland
2016-08-01 19:42 ` Kees Cook
2016-08-03 22:53 ` Catalin Marinas
2016-08-04 5:32 ` Kees Cook
2016-08-04 5:45 ` Andy Lutomirski
2016-08-04 5:54 ` Kees Cook
2016-08-05 0:12 ` Andy Lutomirski
2016-09-08 23:54 ` Kees Cook
2016-09-09 0:42 ` Andy Lutomirski
2016-08-04 14:17 ` Dave Hansen
2016-08-04 22:29 ` Catalin Marinas
2016-08-01 9:34 ` Mark Rutland [this message]
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=20160801093417.GA11119@leverpostej \
--to=mark.rutland@arm.com \
--cc=jann@thejh.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=paul.burton@imgtec.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.