From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
corbet@lwn.net, zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
eric.snowberg@oracle.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
wufan@linux.microsoft.com, pbrobinson@gmail.com,
zbyszek@in.waw.pl, hch@lst.de, mjg59@srcf.ucam.org,
pmatilai@redhat.com, jannh@google.com, dhowells@redhat.com,
jikos@kernel.org, mkoutny@suse.com, ppavlu@suse.com,
petr.vorel@gmail.com, mzerqung@0pointer.de, kgold@linux.ibm.com,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [RFC][PATCH v3 04/10] ima: Add digest_cache_measure/appraise boot-time built-in policies
Date: Fri, 06 Sep 2024 13:25:06 +0200 [thread overview]
Message-ID: <a96e41bd0d4cdc726a80ae24901bcda1e887a65a.camel@huaweicloud.com> (raw)
In-Reply-To: <D3Z3S9Z6B4BC.2OSFJZYTZOPZD@kernel.org>
On Fri, 2024-09-06 at 12:45 +0300, Jarkko Sakkinen wrote:
> On Thu Sep 5, 2024 at 6:25 PM EEST, Roberto Sassu wrote:
> > From: Roberto Sassu <roberto.sassu@huawei.com>
> >
> > Specify the 'digest_cache_measure' boot-time policy with 'ima_policy=' in
> > the kernel command line to add the following rule at the beginning of the
> > IMA policy, before other rules:
> >
> > measure func=DIGEST_LIST_CHECK pcr=12
> >
> > which will measure digest lists into PCR 12 (or the value in
> > CONFIG_IMA_DIGEST_CACHE_MEASURE_PCR_IDX).
> >
> > Specify 'digest_cache_appraise' to add the following rule at the beginning,
> > before other rules:
> >
> > appraise func=DIGEST_LIST_CHECK appraise_type=imasig|modsig
> >
> > which will appraise digest lists with IMA signatures or module-style
> > appended signatures.
> >
> > Adding those rule at the beginning rather than at the end is necessary to
> > ensure that digest lists are measured and appraised in the initial ram
> > disk, which would be otherwise prevented by the dont_ rules.
> >
> > Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> > ---
> > .../admin-guide/kernel-parameters.txt | 10 +++++-
> > security/integrity/ima/Kconfig | 10 ++++++
> > security/integrity/ima/ima_policy.c | 35 +++++++++++++++++++
> > 3 files changed, 54 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 09126bb8cc9f..afaaf125a237 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -2077,7 +2077,8 @@
> > ima_policy= [IMA]
> > The builtin policies to load during IMA setup.
> > Format: "tcb | appraise_tcb | secure_boot |
> > - fail_securely | critical_data"
> > + fail_securely | critical_data |
> > + digest_cache_measure | digest_cache_appraise"
> >
> > The "tcb" policy measures all programs exec'd, files
> > mmap'd for exec, and all files opened with the read
> > @@ -2099,6 +2100,13 @@
> > The "critical_data" policy measures kernel integrity
> > critical data.
> >
> > + The "digest_cache_measure" policy measures digest lists
> > + into PCR 12 (can be changed with kernel config).
> > +
> > + The "digest_cache_appraise" policy appraises digest
> > + lists with IMA signatures or module-style appended
> > + signatures.
> > +
> > ima_tcb [IMA] Deprecated. Use ima_policy= instead.
> > Load a policy which meets the needs of the Trusted
> > Computing Base. This means IMA will measure all
>
> Must be updated as a separate commit as kernel-parameters.txt not
> part of IMA. Consider it as a different subsystem in this context.
Can be done, but this would be more like an atomic change in case the
patch is reverted.
Thanks
Roberto
next prev parent reply other threads:[~2024-09-06 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 15:25 [RFC][PATCH v3 00/10] ima: Integrate with Integrity Digest Cache Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 01/10] ima: Introduce hook DIGEST_LIST_CHECK Roberto Sassu
2024-09-06 9:41 ` Jarkko Sakkinen
2024-09-06 11:22 ` Roberto Sassu
2024-09-06 13:40 ` Jarkko Sakkinen
2024-09-05 15:25 ` [RFC][PATCH v3 02/10] ima: Nest iint mutex for DIGEST_LIST_CHECK hook Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 03/10] ima: Add digest_cache policy keyword Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 04/10] ima: Add digest_cache_measure/appraise boot-time built-in policies Roberto Sassu
2024-09-06 9:45 ` Jarkko Sakkinen
2024-09-06 11:25 ` Roberto Sassu [this message]
2024-09-05 15:25 ` [RFC][PATCH v3 05/10] ima: Modify existing boot-time built-in policies with digest cache policies Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 06/10] ima: Retrieve digest cache and check if changed Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 07/10] ima: Store verified usage in digest cache based on integrity metadata flags Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 08/10] ima: Load verified usage from digest cache found from query Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 09/10] ima: Use digest caches for measurement Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 10/10] ima: Use digest caches for appraisal Roberto Sassu
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=a96e41bd0d4cdc726a80ae24901bcda1e887a65a.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=jarkko@kernel.org \
--cc=jikos@kernel.org \
--cc=jmorris@namei.org \
--cc=kgold@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mkoutny@suse.com \
--cc=mzerqung@0pointer.de \
--cc=paul@paul-moore.com \
--cc=pbrobinson@gmail.com \
--cc=petr.vorel@gmail.com \
--cc=pmatilai@redhat.com \
--cc=ppavlu@suse.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=wufan@linux.microsoft.com \
--cc=zbyszek@in.waw.pl \
--cc=zohar@linux.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
all inboxes | Powered by JetHome®