[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CY6WDWW69XDP.2E8GFRMXYTB22@suppilovahvero>
Date: Fri, 05 Jan 2024 18:02:38 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Coiby Xu" <coxu@...hat.com>
Cc: <linux-integrity@...r.kernel.org>, <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 Fri Jan 5, 2024 at 3:20 PM EET, Coiby Xu wrote:
> On Wed, Jan 03, 2024 at 04:09:29PM +0200, Jarkko Sakkinen wrote:
> >On Wed Dec 27, 2023 at 6:41 AM EET, Coiby Xu 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
> >
> >Missing "Firstname Lastname".
>
> Thanks for raising this concern! I've asked the reporter if he/she can
> share his/her name.
Also, it is lacking fixes tag.
Fixes tag is mandatory, name part would be super nice to have :-) Since
this categories as a bug fix, getting them in is 1st priority and that
thus does not absolutely block applying the change. Thanks for going
trouble trying to query it, however.
BR, Jarkko
Powered by blists - more mailing lists