From: "Serge E. Hallyn" <serge@hallyn.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Milan Broz <gmazyland@gmail.com>,
Eric Biggers <ebiggers@kernel.org>,
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>, Tycho Andersen <tycho@tycho.ws>,
Mike McCracken <mikmccra@cisco.com>
Subject: Re: [PATCH] dm verity: fallback to platform keyring also if key in trusted keyring is rejected
Date: Wed, 25 Sep 2024 07:57:17 -0500 [thread overview]
Message-ID: <20240925125717.GA653365@mail.hallyn.com> (raw)
In-Reply-To: <D4F8UQ7EQ1AH.28Y6BJIM287S1@kernel.org>
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? ;-)
It gets used for integrity guarantees in certain containers, where
the layers of tarballs are replaced by layers of squashfs, with the
dmverity root hash for each layer listed in the signed manifest, e.g.
github.com/project-stacker/stacker
github.com/project-machine/atomfs
This is used of course to verify container integrity, and also gets used by
some projects and products to create an RFS from such images during initrd
github.com/project-machine/mos
-serge
next prev parent reply other threads:[~2024-09-25 12:57 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 [this message]
2024-09-25 14:50 ` Jarkko Sakkinen
2024-09-25 16:53 ` Eric Biggers
2024-09-25 17:15 ` Jarkko Sakkinen
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=20240925125717.GA653365@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=dhowells@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=luca.boccassi@gmail.com \
--cc=mikmccra@cisco.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=tycho@tycho.ws \
--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