From: Mimi Zohar <zohar@linux.ibm.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
linux-integrity@vger.kernel.org
Subject: Re: IMA's use of the audit rule code
Date: Thu, 02 Jan 2020 14:18:27 -0500 [thread overview]
Message-ID: <1577992707.5874.110.camel@linux.ibm.com> (raw)
In-Reply-To: <a6c15a35-a8cb-7589-7960-a19e788b6c45@schaufler-ca.com>
On Thu, 2020-01-02 at 09:06 -0800, Casey Schaufler wrote:
> IMA refines security_audit_rule_init to security_filter_rule_init.
> I need to understand what, if any, relationship there is between
> IMA's use of the audit rule mechanisms and the audit system's use.
> Is this simple code reuse, or is there some interaction between IMA
> and audit?
>
> I'm trying to sort out the problem of audit rules when
> there are multiple security modules. It looks as if there is also a
> problem for integrity rules, but it looks different. The "easy"
> change for audit doesn't fit with what's in IMA. If there's no
> interaction between the IMA and audit use of the rule infrastructure
> it's reasonable to fix them separately. If there is interaction
> things get messy.
They're both comparing rules with LSM labels. In IMA's case, the LSM
labels are used to identify which files are in/out of the IMA policy -
"measurement", "appraisal", and "audit". I'm not sure how different
this is than the audit subsystem.
Mimi
next prev parent reply other threads:[~2020-01-02 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a6c15a35-a8cb-7589-7960-a19e788b6c45.ref@schaufler-ca.com>
2020-01-02 17:06 ` IMA's use of the audit rule code Casey Schaufler
2020-01-02 19:18 ` Mimi Zohar [this message]
2020-01-02 20:21 ` Casey Schaufler
2020-01-02 20:36 ` Mimi Zohar
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=1577992707.5874.110.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=linux-integrity@vger.kernel.org \
/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.