[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6173db54e3d75481a6b1f1079c5b06e1c1caf564.camel@linux.ibm.com>
Date: Wed, 12 Jul 2023 13:40:33 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Eric Snowberg <eric.snowberg@...cle.com>
Cc: dmitry.kasatkin@...il.com, paul@...l-moore.com, jmorris@...ei.org,
serge@...lyn.com, roberto.sassu@...wei.com,
kanth.ghatraju@...cle.com, konrad.wilk@...cle.com,
linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH v2] integrity: Always reference the blacklist keyring
with apprasial
On Wed, 2023-07-05 at 18:52 -0400, Eric Snowberg wrote:
> Commit 273df864cf746 ("ima: Check against blacklisted hashes for files with
> modsig") introduced an appraise_flag option for referencing the blacklist
> keyring. Any matching binary found on this keyring fails signature
> validation. This flag only works with module appended signatures.
>
> An important part of a PKI infrastructure is to have the ability to do
> revocation at a later time should a vulnerability be found. Expand the
> revocation flag usage to all appraisal functions. The flag is now
> enabled by default. Setting the flag with an IMA policy has been
> deprecated. Without a revocation capability like this in place, only
> authenticity can be maintained. With this change, integrity can now be
> achieved with digital signature based IMA appraisal.
>
> Signed-off-by: Eric Snowberg <eric.snowberg@...cle.com>
Thanks, Eric. Other than including "appraise_flag=check_blacklist"
when displaying the measurement list, it looks good.
--
thanks,
Mimi
Powered by blists - more mailing lists