[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2E548AE0-8029-4BB0-B162-4CAD0544EDB8@oracle.com>
Date: Tue, 2 Jan 2024 17:33:53 +0000
From: Eric Snowberg <eric.snowberg@...cle.com>
To: Coiby Xu <coxu@...hat.com>
CC: "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"itrymybest80@...tonmail.com" <itrymybest80@...tonmail.com>,
Mimi Zohar
<zohar@...ux.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
Paul
Moore <paul@...l-moore.com>, James Morris <jmorris@...ei.org>,
"Serge E.
Hallyn" <serge@...lyn.com>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@...r.kernel.org>,
open list
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] integrity: don't throw an error immediately when failed
to add a cert to the .machine keyring
> On Dec 26, 2023, at 9:41 PM, Coiby Xu <coxu@...hat.com> wrote:
>
> Currently when the kernel fails to add a cert to the .machine keyring,
> it will throw an error immediately in the function integrity_add_key.
>
> Since the kernel will try adding to the .platform keyring next or throw
> an error (in the caller of integrity_add_key i.e. add_to_machine_keyring),
> so there is no need to throw an error immediately in integrity_add_key.
>
> Reported-by: itrymybest80@...tonmail.com
> Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2239331
> Signed-off-by: Coiby Xu <coxu@...hat.com>
Reviewed-by: Eric Snowberg <eric.snowberg@...cle.com>
Powered by blists - more mailing lists