From: Vivek Goyal <vgoyal@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ima: Support appraise_type=imasig_optional
Date: Tue, 12 Feb 2013 13:57:25 -0500 [thread overview]
Message-ID: <20130212185725.GC23410@redhat.com> (raw)
In-Reply-To: <20130212185203.GA29958@redhat.com>
On Tue, Feb 12, 2013 at 01:52:03PM -0500, Vivek Goyal wrote:
> On Tue, Feb 12, 2013 at 12:14:07PM -0500, Mimi Zohar wrote:
>
> [..]
> > > > > --- a/security/integrity/ima/ima_appraise.c
> > > > > +++ b/security/integrity/ima/ima_appraise.c
> > > > > @@ -124,19 +124,26 @@ int ima_appraise_measurement(int func, struct integrity_iint_cache *iint,
> > > > > enum integrity_status status = INTEGRITY_UNKNOWN;
> > > > > const char *op = "appraise_data";
> > > > > char *cause = "unknown";
> > > > > - int rc;
> > > > > + int rc, audit_info = 0;
> > > > >
> > > > > if (!ima_appraise)
> > > > > return 0;
> > > > > - if (!inode->i_op->getxattr)
> > > > > + if (!inode->i_op->getxattr) {
> > > > > + /* getxattr not supported. file couldn't have been signed */
> > > > > + if (iint->flags & IMA_DIGSIG_OPTIONAL)
> > > > > + return INTEGRITY_PASS;
> > > > > return INTEGRITY_UNKNOWN;
> > > > > + }
> > > > >
> > > >
> > > > Please don't change the result of the appraisal like this. A single
> > > > change can be made towards the bottom of process_measurement().
> > >
> > > I don't want to pass integrity in all cases of INTEGRITY_UNKNOWN. So
> > > I can probably maintain a bool variable, say pass_appraisal, and set
> > > that here and at the end of function, parse that variable and change
> > > the status accordingly.
> >
> > process_measurement() is the only caller of ima_appraise_measurement().
> > Leave the results of ima_appraise_measurement() alone. There's already
> > code at the end of process_measurement() which decides what to return.
> > Just modify it based on the appraisal results.
>
If we do this, audit logs will be filled with integrity unknown failures.
As each unsigned executable file will fail appraisal with INTEGRITY_UNKNOWN
and an audit message will be logged.
Thanks
Vivek
next prev parent reply other threads:[~2013-02-12 18:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 20:11 [RFC PATCH 0/2] ima: Support a mode to appraise signed files only Vivek Goyal
2013-02-11 20:11 ` [PATCH 1/2] ima: Do not try to fix hash if file system does not support security xattr Vivek Goyal
2013-02-12 11:45 ` Mimi Zohar
2013-02-12 14:27 ` Vivek Goyal
2013-02-11 20:11 ` [PATCH 2/2] ima: Support appraise_type=imasig_optional Vivek Goyal
2013-02-11 22:10 ` Mimi Zohar
2013-02-12 14:26 ` Vivek Goyal
2013-02-12 17:14 ` Mimi Zohar
2013-02-12 18:52 ` Vivek Goyal
2013-02-12 18:57 ` Vivek Goyal [this message]
2013-02-13 12:14 ` Kasatkin, Dmitry
2013-02-13 13:29 ` Vivek Goyal
2013-02-13 13:36 ` Kasatkin, Dmitry
2013-02-13 13:49 ` Vivek Goyal
2013-02-13 14:03 ` Mimi Zohar
2013-02-13 14:38 ` Vivek Goyal
2013-02-13 15:26 ` Kasatkin, Dmitry
2013-02-13 15:29 ` Kasatkin, Dmitry
2013-02-13 15:39 ` Vivek Goyal
2013-02-13 15:30 ` Vivek Goyal
2013-02-13 22:27 ` Mimi Zohar
2013-02-14 15:03 ` Vivek Goyal
2013-02-14 15:30 ` Mimi Zohar
2013-02-18 18:21 ` Vivek Goyal
2013-02-19 21:54 ` Mimi Zohar
2013-02-13 15:51 ` Mimi Zohar
2013-02-12 20:05 ` Mimi Zohar
2013-02-13 12:31 ` Kasatkin, Dmitry
2013-02-13 12:56 ` Mimi Zohar
2013-02-13 13:13 ` Kasatkin, Dmitry
2013-02-13 13:44 ` Mimi Zohar
2013-02-13 16:59 ` Vivek Goyal
2013-02-14 12:57 ` Mimi Zohar
2013-02-14 15:23 ` Vivek Goyal
2013-02-14 15:35 ` Mimi Zohar
2013-02-14 16:17 ` Vivek Goyal
2013-02-14 16:31 ` Vivek Goyal
2013-02-14 19:49 ` Mimi Zohar
2013-02-14 20:54 ` Vivek Goyal
2013-02-14 20:57 ` Vivek Goyal
2013-02-14 21:54 ` Mimi Zohar
2013-02-13 17:33 ` Kasatkin, Dmitry
2013-02-13 17:51 ` Vivek Goyal
2013-02-13 18:20 ` Kasatkin, Dmitry
2013-02-13 21:45 ` Mimi Zohar
2013-02-14 14:40 ` Vivek Goyal
2013-02-14 15:48 ` 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=20130212185725.GC23410@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox