From: Igor Zhbanov <i.zhbanov@omprussia.ru>
To: Mimi Zohar <zohar@linux.ibm.com>, Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
Jann Horn <jannh@google.com>
Subject: Re: Should mprotect(..., PROT_EXEC) be checked by IMA?
Date: Thu, 21 Mar 2019 14:48:09 +0300 [thread overview]
Message-ID: <dab923ca-ef53-4af2-034a-bea4151a4e25@omprussia.ru> (raw)
In-Reply-To: <1553167318.4899.382.camel@linux.ibm.com>
On 21.03.2019 14:21, Mimi Zohar wrote:
> <snip>
> Igor, as for shared libraries:
>
> 1. Extend ima_file_mmap() to permit, based on policy, verifying file
> signatures for files being mmap'ed read and preventing validly signed
> files from being mmap'ed write.
>
> 2. Define an IMA mprotect hook that permits, based on policy,
> preventing memory having validly signed backing storage from setting
> the memory region to write, but allow execute.
>
> (This will require access to the IMA mmap signature verification
> status cached in the "iint".)
Yes, it could work.
Pages mapped from the signed backing store rarely need to be altered
so preventing them from being changed will work.
Along with disabling creating anonymous executable pages at all since
is is hardly needed for the system services for normal work.
It could block polymorphic code so only ROP (return-oriented programming)
could survive after intercepting of execution flow without having an ability
to download any extra code from their servers.
next prev parent reply other threads:[~2019-03-21 11:48 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 [this message]
2019-03-21 18:04 ` Matthew Garrett
2019-03-22 7:59 ` Igor Zhbanov
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=dab923ca-ef53-4af2-034a-bea4151a4e25@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.