[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c88c5bb9523674be2ecfc49d093b16a42220a53.camel@linux.ibm.com>
Date: Wed, 15 Dec 2021 22:54:42 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Stefan Berger <stefanb@...ux.ibm.com>,
linux-integrity@...r.kernel.org
Cc: serge@...lyn.com, christian.brauner@...ntu.com,
containers@...ts.linux.dev, dmitry.kasatkin@...il.com,
ebiederm@...ssion.com, krzysztof.struczynski@...wei.com,
roberto.sassu@...wei.com, mpeters@...hat.com, lhinds@...hat.com,
lsturman@...hat.com, puiterwi@...hat.com, jejb@...ux.ibm.com,
jamjoom@...ibm.com, linux-kernel@...r.kernel.org,
paul@...l-moore.com, rgb@...hat.com,
linux-security-module@...r.kernel.org, jmorris@...ei.org,
Mehmet Kayaalp <mkayaalp@...ux.vnet.ibm.com>
Subject: Re: [PATCH v6 03/17] ima: Namespace audit status flags
On Wed, 2021-12-15 at 21:38 -0500, Stefan Berger wrote:
> On 12/15/21 16:15, Mimi Zohar wrote:
> > On Fri, 2021-12-10 at 14:47 -0500, Stefan Berger wrote:
> >> From: Mehmet Kayaalp <mkayaalp@...ux.vnet.ibm.com>
> >>
> >> The iint cache stores whether the file is measured, appraised, audited
> >> etc. This patch moves the IMA_AUDITED flag into the per-namespace
> >> ns_status, enabling IMA audit mechanism to audit the same file each time
> >> it is accessed in a new namespace.
> >>
> >> The ns_status is not looked up if the CONFIG_IMA_NS is disabled or if
> >> any of the IMA_NS_STATUS_ACTIONS (currently only IMA_AUDIT) is not
> >> enabled.
> > ^none of the ... are enabled.
>
> You want me to rephrase it?
Yes, please.
thanks,
Mimi
Powered by blists - more mailing lists