mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: "Mickaël Salaün" <mic@linux.microsoft.com>,
	"Jarkko Sakkinen" <jarkko@kernel.org>,
	"David Howells" <dhowells@redhat.com>,
	"David Woodhouse" <dwmw2@infradead.org>,
	keyrings@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Mark Pearson <markpearson@lenovo.com>
Subject: [BUG] blacklist: Problem blacklisting hash (-13) during boot
Date: Sat, 15 Oct 2022 05:16:49 +0200	[thread overview]
Message-ID: <c8c65713-5cda-43ad-8018-20f2e32e4432@t-8ch.de> (raw)

Hi,

Since 5.19 during boot I see lots of the following entries in dmesg:

blacklist: Problem blacklisting hash (-13)

This happens because the firmware contains duplicate blacklist entries.
As commit 6364d106e041 [0] modified the "blacklist" keyring to reject updates
this now leads to the spurious error messages.

The machine is a Thinkpad X1 Cargon Gen9 with BIOS revision 1.56 and firmware
revision 1.33.

[0] 6364d106e041 ("certs: Allow root user to append signed hashes to the blacklist keyring")

             reply	other threads:[~2022-10-15  3:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15  3:16 Thomas Weißschuh [this message]
2022-11-04 17:03 ` 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
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=c8c65713-5cda-43ad-8018-20f2e32e4432@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markpearson@lenovo.com \
    --cc=mic@linux.microsoft.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®