From: Lev Olshvang <levonshe@yandex.com>
To: linux-il <linux-il@cs.huji.ac.il>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: SELinux, LSM and ima_policy rules
Date: Mon, 04 Feb 2019 11:38:19 +0300 [thread overview]
Message-ID: <25111041549269499@myt6-67cd1de25d8a.qloud-c.yandex.net> (raw)
Hello everybody.
I learned recently that IMA kernel security subsystem can be integrated with LSMs, such as SELinux, Smack, ...
https://sourceforge.net/p/linux-ima/wiki/Home/
https://www.kernel.org/doc/Documentation/ABI/testing/ima_policy
It was present in kernel since v3.8 but not google does not know much about the usability.
Does anybody have any experience or references which I can read to learn restrictions, performance impact or just use cases?
ThanX!
Lev.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-02-04 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 8:38 Lev Olshvang [this message]
2019-02-04 22:06 ` SELinux, LSM and ima_policy rules valdis.kletnieks
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=25111041549269499@myt6-67cd1de25d8a.qloud-c.yandex.net \
--to=levonshe@yandex.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-il@cs.huji.ac.il \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).