linux-kernel - Re: [PATCH 31/32] x86, pkeys: execute-only support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALCETrXhNXx_csPnXcSaPvgY52NN8kadvd8XG8FQ3dcMfvftOg@mail.gmail.com>
Date:	Mon, 14 Dec 2015 15:47:24 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Dave Hansen <dave@...1.net>
Cc:	Kees Cook <keescook@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux-MM <linux-mm@...ck.org>, "x86@...nel.org" <x86@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH 31/32] x86, pkeys: execute-only support

On Mon, Dec 14, 2015 at 3:44 PM, Dave Hansen <dave@...1.net> wrote:
> On 12/14/2015 03:39 PM, Andy Lutomirski wrote:
>>> > Nope.  My linker-fu is weak.
>>> >
>>> > Can we even depend on the linker by itself?  Even if the sections were
>>> > marked --x, we can't actually use them with those permissions unless we
>>> > have protection keys.
>>> >
>>> > Do we need some special tag on the section to tell the linker to map it
>>> > as --x under some conditions and r-x for others?
>>> >
>> Why?  Wouldn't --x just end up acting like r-x if PKRU is absent?
>
> An app doing --x would expect it to be unreadable.  I don't think we can
> just silently turn it in to r-x.

I don't see why.  After all, an app doing --x right now gets rx.  An
app doing r-- still gets r-x on some systems.

--Andy


-- 
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/