From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Igor Zhbanov <i.zhbanov@omprussia.ru>,
Matthew Garrett <mjg59@google.com>,
Kees Cook <keescook@chromium.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Paul Moore <paul@paul-moore.com>,
John Johansen <john.johansen@canonical.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Jann Horn <jannh@google.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: Should mprotect(..., PROT_EXEC) be checked by IMA?
Date: Fri, 29 Mar 2019 11:51:41 +0000 [thread overview]
Message-ID: <qVt5eJGvmcoQ8hfVSs5S4nXQ_3dFyZne8vIO0fNgJevhW19XHIaJxnlBMlDfUOanUoTjTk5bLes-9ipnzoLSg1xciMA4zivRRFkaTHp5YWQ=@protonmail.ch> (raw)
In-Reply-To: <1553857187.9420.49.camel@linux.ibm.com>
On Friday, March 29, 2019 10:59 AM, Mimi Zohar <zohar@linux.ibm.com> wrote:
> [Cc'ing the LSM mailing list and others]
>
> On Fri, 2019-03-29 at 13:00 +0300, Igor Zhbanov wrote:
>
> > Hi Mimi,On 28.03.2019 20:17, Mimi Zohar wrote:
>
> > > I just came across the grsecurity article on mprotect.[1]
> > > Has anyone looked at it? Would it make sense to make it a minor LSM?
> > > [1]https://pax.grsecurity.net/docs/mprotect.txt
> >
> > Interesting article. It is almost exactly of what I wanted to be implemented.
> > If this minor LSM would be stackable to allow combining with e.g. SELinux
> > then why not.
>
> Stacking shouldn't be a problem. Other LSMs are already on the
> mprotect hook. Let's hear what others think.
>
> Mimi
There is already minor LSM in progress: https://sara.smeso.it/en/latest/
Jordan
next prev parent reply other threads:[~2019-03-29 11:51 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
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 [this message]
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='qVt5eJGvmcoQ8hfVSs5S4nXQ_3dFyZne8vIO0fNgJevhW19XHIaJxnlBMlDfUOanUoTjTk5bLes-9ipnzoLSg1xciMA4zivRRFkaTHp5YWQ=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=casey@schaufler-ca.com \
--cc=i.zhbanov@omprussia.ru \
--cc=jannh@google.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--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.