From: Mark Pearson <markpearson@lenovo.com>
To: "Jeremy Kerr" <jk@codeconstruct.com.au>,
"Thomas Weißschuh" <thomas@t-8ch.de>,
"Mickaël Salaün" <mic@digikod.net>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>, <keyrings@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>
Subject: Re: [External] Re: [BUG] blacklist: Problem blacklisting hash (-13) during boot
Date: Mon, 27 Feb 2023 08:38:05 -0500 [thread overview]
Message-ID: <2a215e4d-bf55-b063-3f1f-a63f51cbdbfb@lenovo.com> (raw)
In-Reply-To: <fec5e8eb3803068a11267f386ddda389a1211736.camel@codeconstruct.com.au>
Hi
On 2/25/23 22:42, Jeremy Kerr wrote:
> Hi Mark,
>
>> I have flagged this to the FW team (LO-2105) to get their feedback
>> and see if we can get it addressed on our platforms.
> Any progress from the FW team about this? I have a fresh-out-of-the-box
> T14s with this issue, there's 33 duplicated hashes in dbx:
I've been looking at this and the FW team are claiming that it's not
caused by duplicate entries in the dbx table, which is honestly a bit
confusing.
We've been doing some more digging - but is there a possibility this is
caused by something else? I was poking around at the kernel code but
haven't got to the bottom of it yet.
Mark
next prev parent reply other threads:[~2023-02-27 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8c65713-5cda-43ad-8018-20f2e32e4432@t-8ch.de>
2022-11-04 17:03 ` [BUG] blacklist: Problem blacklisting hash (-13) during boot Mickaël Salaün
2022-11-04 19:11 ` Thomas Weißschuh
2022-11-04 20:12 ` [External] " Mark Pearson
2023-02-26 3:42 ` Jeremy Kerr
2023-02-26 4:28 ` Thomas Weißschuh
2023-02-27 1:42 ` Jeremy Kerr
2023-02-27 13:38 ` Mark Pearson [this message]
2023-02-27 14:36 ` Jeremy Kerr
2023-03-07 13:45 ` Mark Pearson
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=2a215e4d-bf55-b063-3f1f-a63f51cbdbfb@lenovo.com \
--to=markpearson@lenovo.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jarkko@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=thomas@t-8ch.de \
/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