From: Petko Manolov <petkan@mip-labs.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
dmitry.kasatkin@gmail.com, james.l.morris@oracle.com,
serge@hallyn.com, linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IMA: policy can be updated zero times
Date: Wed, 23 Dec 2015 13:47:21 +0200 [thread overview]
Message-ID: <20151223114721.GG5662@localhost> (raw)
In-Reply-To: <5679C589.1060102@oracle.com>
On 15-12-22 16:50:01, Sasha Levin wrote:
> On 12/22/2015 04:40 PM, Petko Manolov wrote:
> >> Thanks, Sasha. By the time ima_update_policy() is called
> >> >ima_release_policy() has already output the policy update status
> >> >message. I guess an empty policy could be considered a valid policy.
> >> >Could you add a msg indicating that the new policy was empty?
> >
> > As far as I can say we can't get to ima_update_policy() with empty
> > ima_temp_rules because ima_write_policy() will set valid_policy to 0 in case
> > of an empty rule. I'll double check it tomorrow, but please you do that
> > too.
>
> This is based on an actual crash rather than code analysis.
I was able to reproduce the crash with: echo "" > /sys/kernel/security/ima/policy
It turns out ima_parse_add_rule() returns 1, even though the string is empty
This logic may be part of "empty policy is a valid policy" or something else.
As it is more dangerous to change the behavior at this point i assume your patch
is the right solution for the problem.
Acked-by: Petko Manolov <petkan@mip-labs.com>
Mimi, shall we change ima_parse_add_rule's behavior in the future or it's too
much work?
cheers,
Petko
next prev parent reply other threads:[~2015-12-23 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 13:51 [PATCH] IMA: policy can be updated zero times Sasha Levin
2015-12-22 19:56 ` Mimi Zohar
2015-12-22 21:40 ` Petko Manolov
2015-12-22 21:50 ` Sasha Levin
2015-12-23 11:47 ` Petko Manolov [this message]
2015-12-23 12:24 ` Mimi Zohar
2015-12-23 12:47 ` [Linux-ima-devel] " 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=20151223114721.GG5662@localhost \
--to=petkan@mip-labs.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=james.l.morris@oracle.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=serge@hallyn.com \
--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