From: Petko Manolov <petkan@nucleusys.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: "Mark D. Baushke" <mdb@juniper.net>,
Petko Manolov <petkan@mip-labs.com>,
linux-integrity@vger.kernel.org
Subject: Re: Cleaning up IMA
Date: Fri, 18 May 2018 18:58:03 +0300 [thread overview]
Message-ID: <20180518155803.GB4816@carbon> (raw)
In-Reply-To: <1526657654.3404.17.camel@linux.vnet.ibm.com>
On 18-05-18 11:34:14, Mimi Zohar wrote:
> On Fri, 2018-05-18 at 07:06 -0700, Mark D. Baushke wrote:
> > Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
> >
> > > On Fri, 2018-05-18 at 13:44 +0000, Mark Baushke wrote:
> > > > Hi Mimi,
> > > >
> > > > I see that Petko has already provide the answer and an updated patch.
> > > >
> > > > I was off-line most of yesterday, and am only now catching up on email.
> > > >
> > > > To confirm, yes, we are still using the ima_update_policy() code.
>
> Updating the policy wasn't the question. It was about using the IMA blacklist,
> as opposed to the system blacklist.
The system-wide blacklist is populated at build time only. This means that you
need kernel change if you want to revoke a certificate, which is sub-optimal.
To be useful for us it should be able to accept imports at run-time.
Until the system-wide blacklist keyring doesn't have this functionality i
suggest that we keep .ima_blacklist around.
Petko
next parent reply other threads:[~2018-05-18 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1526580423.3632.17.camel@linux.vnet.ibm.com>
[not found] ` <92E32D97-B60A-4D75-AC9F-594F95E432B1@juniper.net>
[not found] ` <1526651759.3632.172.camel@linux.vnet.ibm.com>
[not found] ` <9298.1526652376@eng-mail01.juniper.net>
[not found] ` <1526657654.3404.17.camel@linux.vnet.ibm.com>
2018-05-18 15:58 ` Petko Manolov [this message]
2018-05-18 16:08 ` Cleaning up IMA Mark Baushke
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=20180518155803.GB4816@carbon \
--to=petkan@nucleusys.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mdb@juniper.net \
--cc=petkan@mip-labs.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