All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: jmorris@namei.org, agk@redhat.com, snitzer@kernel.org,
	mka@chromium.org, serge@hallyn.com
Cc: Kees Cook <keescook@chromium.org>,
	linux-raid@vger.kernel.org, song@kernel.org,
	dianders@chromium.org, linux-security-module@vger.kernel.org,
	dm-devel@redhat.com, gmazyland@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Fri,  8 Jul 2022 10:47:59 -0700	[thread overview]
Message-ID: <165730247648.3882109.12888837825450019581.b4-ty@chromium.org> (raw)
In-Reply-To: <20220627153526.3750341-1-mka@chromium.org>

On Mon, 27 Jun 2022 08:35:23 -0700, Matthias Kaehlcke wrote:
> As of now LoadPin restricts loading of kernel files to a single pinned
> filesystem, typically the rootfs. This works for many systems, however it
> can result in a bloated rootfs (and OTA updates) on platforms where
> multiple boards with different hardware configurations use the same rootfs
> image. Especially when 'optional' files are large it may be preferable to
> download/install them only when they are actually needed by a given board.
> Chrome OS uses Downloadable Content (DLC) [1] to deploy certain 'packages'
> at runtime. As an example a DLC package could contain firmware for a
> peripheral that is not present on all boards. DLCs use dm-verity [2] to
> verify the integrity of the DLC content.
> 
> [...]

Applied to for-next/hardening, thanks!

[1/3] dm: Add verity helpers for LoadPin
      https://git.kernel.org/kees/c/b6c1c5745ccc
[2/3] LoadPin: Enable loading from trusted dm-verity devices
      https://git.kernel.org/kees/c/3f805f8cc23b
[3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation
      https://git.kernel.org/kees/c/231af4709018

-- 
Kees Cook


WARNING: multiple messages have this Message-ID
From: Kees Cook <keescook@chromium.org>
To: jmorris@namei.org, agk@redhat.com, snitzer@kernel.org,
	mka@chromium.org, serge@hallyn.com
Cc: Kees Cook <keescook@chromium.org>,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	dianders@chromium.org, linux-raid@vger.kernel.org,
	song@kernel.org, linux-security-module@vger.kernel.org,
	gmazyland@gmail.com
Subject: Re: [dm-devel] [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Fri,  8 Jul 2022 10:47:59 -0700	[thread overview]
Message-ID: <165730247648.3882109.12888837825450019581.b4-ty@chromium.org> (raw)
In-Reply-To: <20220627153526.3750341-1-mka@chromium.org>

On Mon, 27 Jun 2022 08:35:23 -0700, Matthias Kaehlcke wrote:
> As of now LoadPin restricts loading of kernel files to a single pinned
> filesystem, typically the rootfs. This works for many systems, however it
> can result in a bloated rootfs (and OTA updates) on platforms where
> multiple boards with different hardware configurations use the same rootfs
> image. Especially when 'optional' files are large it may be preferable to
> download/install them only when they are actually needed by a given board.
> Chrome OS uses Downloadable Content (DLC) [1] to deploy certain 'packages'
> at runtime. As an example a DLC package could contain firmware for a
> peripheral that is not present on all boards. DLCs use dm-verity [2] to
> verify the integrity of the DLC content.
> 
> [...]

Applied to for-next/hardening, thanks!

[1/3] dm: Add verity helpers for LoadPin
      https://git.kernel.org/kees/c/b6c1c5745ccc
[2/3] LoadPin: Enable loading from trusted dm-verity devices
      https://git.kernel.org/kees/c/3f805f8cc23b
[3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation
      https://git.kernel.org/kees/c/231af4709018

-- 
Kees Cook

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


  parent reply	other threads:[~2022-07-08 17:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 15:35 [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-06-27 15:35 ` [dm-devel] " Matthias Kaehlcke
2022-06-27 15:35 ` [PATCH v7 1/3] dm: Add verity helpers for LoadPin Matthias Kaehlcke
2022-06-27 15:35   ` [dm-devel] " Matthias Kaehlcke
2022-07-06 15:06   ` Mike Snitzer
2022-07-06 15:06     ` [dm-devel] " Mike Snitzer
2022-06-27 15:35 ` [PATCH v7 2/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-06-27 15:35   ` [dm-devel] " Matthias Kaehlcke
2022-07-06 15:08   ` Mike Snitzer
2022-07-06 15:08     ` [dm-devel] " Mike Snitzer
2022-06-27 15:35 ` [PATCH v7 3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation Matthias Kaehlcke
2022-06-27 15:35   ` [dm-devel] " Matthias Kaehlcke
2022-07-06 15:09   ` Mike Snitzer
2022-07-06 15:09     ` [dm-devel] " Mike Snitzer
2022-07-06 15:11 ` [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices Mike Snitzer
2022-07-06 15:11   ` [dm-devel] " Mike Snitzer
2022-07-07  3:58   ` Kees Cook
2022-07-07  3:58     ` Kees Cook
2022-07-08 17:47 ` Kees Cook [this message]
2022-07-08 17:47   ` [dm-devel] " Kees Cook

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=165730247648.3882109.12888837825450019581.b4-ty@chromium.org \
    --to=keescook@chromium.org \
    --cc=agk@redhat.com \
    --cc=dianders@chromium.org \
    --cc=dm-devel@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=serge@hallyn.com \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.