Messages in this thread | | | Subject | Re: [PATCH 26/26] x86, pkeys: Documentation | From | Dave Hansen <> | Date | Thu, 1 Oct 2015 13:58:04 -0700 |
| |
On 10/01/2015 01:39 PM, Kees Cook wrote: > On Thu, Oct 1, 2015 at 4:17 AM, Ingo Molnar <mingo@kernel.org> wrote: >> * Dave Hansen <dave@sr71.net> wrote: >>>> If yes then this could be a significant security feature / usecase for pkeys: > > Which CPUs (will) have pkeys?
It hasn't been announced publicly, so all I can say here is "future ones".
>>>> executable sections of shared libraries and binaries could be mapped with pkey >>>> access disabled. If I read the Intel documentation correctly then that should >>>> be possible. >>> >>> Agreed. I've even heard from some researchers who are interested in this: >>> >>> https://www.infsec.cs.uni-saarland.de/wp-content/uploads/sites/2/2014/10/nuernberger2014ccs_disclosure.pdf >> >> So could we try to add an (opt-in) kernel option that enables this transparently >> and automatically for all PROT_EXEC && !PROT_WRITE mappings, without any >> user-space changes and syscalls necessary? > > I would like this very much. :)
I'll go hack something together and see what breaks.
| |