From: Igor Zhbanov <i.zhbanov@omprussia.ru>
To: Matthew Garrett <mjg59@google.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Jann Horn <jannh@google.com>
Subject: Re: Should mprotect(..., PROT_EXEC) be checked by IMA?
Date: Fri, 22 Mar 2019 10:59:12 +0300 [thread overview]
Message-ID: <07347317-ee71-83c1-384a-0c3439980af7@omprussia.ru> (raw)
In-Reply-To: <CACdnJuvVqibDdd+MLKOHqEfdngTk=GSkfybj1jS3MpmC7rjyHg@mail.gmail.com>
On 21.03.2019 21:04, Matthew Garrett wrote:
> On Thu, Mar 21, 2019 at 4:48 AM Igor Zhbanov <i.zhbanov@omprussia.ru> wrote:
>> Along with disabling creating anonymous executable pages at all since
>> is is hardly needed for the system services for normal work.
>
> Is this true? Do no JIT compilers behave this way?
Well, besides JIT I've scanned all /proc/PID/maps of my web-server and didn't
find any process with mapped anonymous executable pages.
As for JIT I suppose we could use prctl or something else to allow having
anonymous executable pages.
I'm pondering about some system-wide (or processes subtree-wide) default
setting controlling whether it is allowed to have anonymous pages by default,
and then some mechanism to turn it on/off on a per-process bases. Perhaps
with some locking preventing reenabling after it was dropped.
And what do you think about it?
next prev parent reply other threads:[~2019-03-22 7:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:18 Should mprotect(..., PROT_EXEC) be checked by IMA? Igor Zhbanov
2019-03-18 21:48 ` Mimi Zohar
2019-03-19 7:50 ` Igor Zhbanov
2019-03-19 11:22 ` Mimi Zohar
2019-03-19 12:19 ` Igor Zhbanov
2019-03-19 17:05 ` Mimi Zohar
2019-03-20 8:11 ` Igor Zhbanov
2019-03-20 17:23 ` Matthew Garrett
2019-03-20 18:08 ` Igor Zhbanov
2019-03-21 11:21 ` Mimi Zohar
2019-03-21 11:48 ` Igor Zhbanov
2019-03-21 18:04 ` Matthew Garrett
2019-03-22 7:59 ` Igor Zhbanov [this message]
2019-03-28 17:17 ` Mimi Zohar
2019-03-29 10:00 ` Igor Zhbanov
2019-03-29 10:59 ` Mimi Zohar
2019-03-29 11:51 ` Jordan Glover
2019-03-29 12:28 ` Stephen Smalley
2019-03-29 12:50 ` Igor Zhbanov
2019-04-02 22:31 ` Matthew Garrett
2019-04-03 9:59 ` Igor Zhbanov
2019-04-03 16:58 ` Matthew Garrett
2019-04-03 17:31 ` Igor Zhbanov
2019-04-03 18:19 ` Matthew Garrett
2019-04-03 18:47 ` Igor Zhbanov
2019-04-03 19:25 ` Matthew Garrett
2019-04-04 11:44 ` Igor Zhbanov
2019-04-03 12:11 ` Mimi Zohar
2019-04-03 13:18 ` Perez Yves-Alexis
2019-04-03 11:57 ` Mimi Zohar
2019-04-03 13:10 ` Stephen Smalley
2019-04-03 14:33 ` Mimi Zohar
2019-04-03 14:33 ` Stephen Smalley
2019-04-03 16:21 ` Mimi Zohar
2019-03-21 18:13 ` Matthew Garrett
2019-03-19 17:07 ` Matthew Garrett
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=07347317-ee71-83c1-384a-0c3439980af7@omprussia.ru \
--to=i.zhbanov@omprussia.ru \
--cc=jannh@google.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=zohar@linux.ibm.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.