From: Mikulas Patocka <mpatocka@redhat.com>
To: Ayoub Zaki <ayoub.zaki@embetrix.com>
Cc: snitzer@kernel.org, agk@redhat.com, bmarzins@redhat.com,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH] dm-verity: add DM_VERITY_VERIFY_ROOTHASH_SIG_FORCE
Date: Mon, 21 Sep 2026 16:14:27 +0200 (CEST) [thread overview]
Message-ID: <9643099f-529f-3417-ab4f-69ca266e736c@redhat.com> (raw)
In-Reply-To: <97f8d660-a523-4011-ba15-6f708cb1b589@embetrix.com>
On Mon, 21 Sep 2026, Ayoub Zaki wrote:
> Hi,
>
>
> On 9/21/26 11:46, Mikulas Patocka wrote:
> > Hi
> >
> > The argument can be turned off even with your patch - by specifying
> > dm_verity.require_signatures=0 on the kernel command line (read-only
> > module parameters can be modified on the command line during boot).
> >
> > I'd like to know what kind of security problem does this patch try to
> > solve. If the attacker can tamper with the kernel command line, he can
> > already gain root (i.e. by using init=/bin/bash).
> >
> > Mikulas
>
> Thanks for reviewing.
> I should have highlighted the change to bool_enable_only: with
> CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_FORCE=y it rejects attempts to clear
> require_signatures, including from the command line.
> I followed the existing CONFIG_MODULE_SIG_FORCE and module.sig_enforce
> implementation.
> My intention is to make signature enforcement a build-time policy rather than
> depend on boot configuration.
OK. I accepted the patch. It will be in 7.4.
Mikulas
> I fully agree with your point and that this patch alone does not protect
> against arbitrary command-line tampering.
>
> If required I can clarify the scope in a v2 ?
prev parent reply other threads:[~2026-09-21 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 17:19 Ayoub Zaki
2026-09-21 10:46 ` Mikulas Patocka
2026-09-21 11:36 ` Ayoub Zaki
2026-09-21 14:14 ` Mikulas Patocka [this message]
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=9643099f-529f-3417-ab4f-69ca266e736c@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=ayoub.zaki@embetrix.com \
--cc=bmarzins@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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 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®