[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2159283.iZASKD2KPV@x2>
Date: Wed, 13 Oct 2021 16:02:30 -0400
From: Steve Grubb <sgrubb@...hat.com>
To: corbet@....net, axboe@...nel.dk, agk@...hat.com,
snitzer@...hat.com, ebiggers@...nel.org, tytso@....edu,
paul@...l-moore.com, eparis@...hat.com, jmorris@...ei.org,
serge@...lyn.com, linux-audit@...hat.com
Cc: linux-security-module@...r.kernel.org, linux-doc@...r.kernel.org,
jannh@...gle.com, linux-fscrypt@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
dm-devel@...hat.com, linux-audit@...hat.com,
deven.desai@...ux.microsoft.com
Subject: Re: [RFC PATCH v7 07/16] ipe: add auditing support
Hello,
On Wednesday, October 13, 2021 3:06:26 PM EDT deven.desai@...ux.microsoft.com
wrote:
> Users of IPE require a way to identify when and why an operation fails,
> allowing them to both respond to violations of policy and be notified
> of potentially malicious actions on their systens with respect to IPE
> itself.
Would you mind sending examples of audit events so that we can see what the
end result is? Some people add them to the commit text. But we still need to
see what they look like.
Thanks,
-Steve
Powered by blists - more mailing lists