From: Milan Broz <gmazyland@gmail.com>
To: Jaskaran Khurana <jaskarankhurana@linux.microsoft.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Cc: agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
jmorris@namei.org, scottsh@microsoft.com, ebiggers@google.com,
mpatocka@redhat.com
Subject: Re: [RFC PATCH v4 1/1] Add dm verity root hash pkcs7 sig validation.
Date: Mon, 17 Jun 2019 15:31:21 +0200 [thread overview]
Message-ID: <ab346931-1d1b-bd2f-8314-ee4779bd44bf@gmail.com> (raw)
In-Reply-To: <20190613010610.4364-2-jaskarankhurana@linux.microsoft.com>
On 13/06/2019 03:06, Jaskaran Khurana wrote:
...
> Adds DM_VERITY_VERIFY_ROOTHASH_SIG_FORCE: roothash signature *must* be
> specified for all dm verity volumes and verification must succeed prior
> to creation of device mapper block device.
I had a quick discussion about this and one suggestion was
to add dm-verity kernel module parameter instead of a new config option.
The idea is that if you can control kernel boot commandline, you can add it
there with the same effect (expecting that root device is on dm-verity as well).
Isn't this better option or it is not going to work for you?
Milan
next prev parent reply other threads:[~2019-06-17 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 1:06 [RFC PATCH v4 0/1] Add dm verity root hash pkcs7 sig validation Jaskaran Khurana
2019-06-13 1:06 ` [RFC PATCH v4 1/1] " Jaskaran Khurana
2019-06-17 13:31 ` Milan Broz [this message]
2019-06-17 20:39 ` Jaskaran Singh Khurana
-- strict thread matches above, loose matches on Subject: below --
2019-06-13 0:43 [RFC PATCH v4 0/1] " Jaskaran Khurana
2019-06-13 0:43 ` [RFC PATCH v4 1/1] " Jaskaran Khurana
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=ab346931-1d1b-bd2f-8314-ee4779bd44bf@gmail.com \
--to=gmazyland@gmail.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=jaskarankhurana@linux.microsoft.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=scottsh@microsoft.com \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).