mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Lorenz Kofler <lorenz@sigma-star.at>,
	Mike Snitzer <snitzer@kernel.org>,
	 Benjamin Marzinski <bmarzins@redhat.com>,
	Alasdair Kergon <agk@redhat.com>,
	 dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	 upstream+dm@sigma-star.at, David Howells <dhowells@redhat.com>,
	 Jarkko Sakkinen <jarkko@kernel.org>,
	keyrings@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] dm-integrity: support keys in the kernel keyring
Date: Fri, 2 Oct 2026 23:09:26 +0200 (CEST)	[thread overview]
Message-ID: <bf54a398-a6b0-a188-85a5-5c3f3fc139fc@redhat.com> (raw)
In-Reply-To: <20261002201419.GA205250@google.com>



On Fri, 2 Oct 2026, Eric Biggers wrote:

> >From what I understand, the point of the keyring support in
> dm-{crypt,inlinecrypt,integrity} is:
> 
> - To support "trusted" keys.  But that is not what was actually
>   implemented in dm-inlinecrypt.
> 
> - To avoid having the key be readable with STATUSTYPE_TABLE.  But that
>   is not what was actually implemented in dm-inlinecrypt.  Keyrings are
>   also unnecesary to solve that problem.
> 
> - To cause security bugs such as https://lwn.net/Articles/1090568/ .
>   Since otherwise things aren't exciting enough, I guess.
> 
> Not sure what I'm missing.
> 
> But if you really do want to support all four key types in all three of
> these targets anyway though, then sure, the code might as well be
> shared since it would otherwise be the same code in each.
> 
> - Eric

Yes, I think that the key support in these targets should be unified.

Mikulas


  reply	other threads:[~2026-10-02 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  6:27 [RFC PATCH 0/1] " Lorenz Kofler
2026-09-28  6:27 ` [RFC PATCH 1/1] " Lorenz Kofler
2026-09-30 15:00   ` Mikulas Patocka
2026-10-02  9:12     ` Lorenz Kofler
2026-10-02 11:48       ` Mikulas Patocka
2026-10-02 20:14         ` Eric Biggers
2026-10-02 21:09           ` Mikulas Patocka [this message]
2026-10-04  7:44           ` 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=bf54a398-a6b0-a188-85a5-5c3f3fc139fc@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenz@sigma-star.at \
    --cc=snitzer@kernel.org \
    --cc=upstream+dm@sigma-star.at \
    /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®