public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>
Cc: "Milan Broz" <gmazyland@gmail.com>,
	"Mikulas Patocka" <mpatocka@redhat.com>,
	<luca.boccassi@gmail.com>, <dm-devel@lists.linux.dev>,
	<snitzer@kernel.org>, <serge@hallyn.com>,
	<wufan@linux.microsoft.com>,
	"David Howells" <dhowells@redhat.com>, <keyrings@vger.kernel.org>,
	<linux-integrity@vger.kernel.org>,
	"Mimi Zohar" <zohar@linux.ibm.com>
Subject: Re: [PATCH] dm verity: fallback to platform keyring also if key in trusted keyring is rejected
Date: Wed, 25 Sep 2024 20:15:01 +0300	[thread overview]
Message-ID: <D4FJ95EVCW7I.2GHRW7LZRZPBJ@kernel.org> (raw)
In-Reply-To: <20240925165338.GA3738787@google.com>

On Wed Sep 25, 2024 at 7:53 PM EEST, Eric Biggers wrote:
> On Wed, Sep 25, 2024 at 12:05:59PM +0300, Jarkko Sakkinen wrote:
> > On Wed Sep 25, 2024 at 11:03 AM EEST, Milan Broz wrote:
> > > >> Doesn't dm-verity have a maintainer?
> > >
> > > (This reminds me of a nice comment from Neil about "little walled
> > > gardens" between MD & DM.  Apparently it applies to other subsystems
> > > as well. Sorry, I couldn't resist to mention it :-)
> > 
> > Np, it's just that last and only time I've ever read anything about
> > dm-verity was 2011 article :-)
> > 
> > I will rephrase question: does dm-verity have a user? ;-)
> > 
> > BR, Jarkko
>
> Sorry if I was unclear.  dm-verity is widely used, including by all Android and
> Chrome OS devices.  But this patch is about dm-verity's in-kernel signature
> verification which is an optional sub-feature that is not widely used.  That
> sub-feature is apparently difficult to test and not clearly specified, which is
> why people seem to be struggling a bit with this patch.

NP, I learned a new thing ;-)

Before Linux I worked with Symbian (ugh) so this whole scheme for doing
FW updates is familiar to me from the dark ages...

And I acked the change too!

> - Eric

BR, Jarkko

  reply	other threads:[~2024-09-25 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240922161753.244476-1-luca.boccassi@gmail.com>
2024-09-23 14:04 ` [PATCH] dm verity: fallback to platform keyring also if key in trusted keyring is rejected Mikulas Patocka
2024-09-24 15:54   ` Jarkko Sakkinen
2024-09-24 18:27     ` Mikulas Patocka
2024-09-24 21:36       ` Jarkko Sakkinen
2024-09-24 21:59         ` Eric Biggers
2024-09-25  7:51           ` Jarkko Sakkinen
2024-09-25  8:03           ` Milan Broz
2024-09-25  9:05             ` Jarkko Sakkinen
2024-09-25 12:57               ` Serge E. Hallyn
2024-09-25 14:50                 ` Jarkko Sakkinen
2024-09-25 16:53               ` Eric Biggers
2024-09-25 17:15                 ` Jarkko Sakkinen [this message]
2024-09-25 21:28             ` Luca Boccassi
2024-09-27  7:12               ` Milan Broz

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=D4FJ95EVCW7I.2GHRW7LZRZPBJ@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=gmazyland@gmail.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=luca.boccassi@gmail.com \
    --cc=mpatocka@redhat.com \
    --cc=serge@hallyn.com \
    --cc=snitzer@kernel.org \
    --cc=wufan@linux.microsoft.com \
    --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