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 v3 0/1] Add dm verity root hash pkcs7 sig validation.
Date: Sat, 8 Jun 2019 10:46:19 +0200 [thread overview]
Message-ID: <3f9f2df1-c811-18d4-2665-0ffddb7a7f0e@gmail.com> (raw)
In-Reply-To: <20190607223140.16979-1-jaskarankhurana@linux.microsoft.com>
On 08/06/2019 00:31, Jaskaran Khurana wrote:
> This patch set adds in-kernel pkcs7 signature checking for the roothash of
> the dm-verity hash tree.
> The verification is to support cases where the roothash is not secured by
> Trusted Boot, UEFI Secureboot or similar technologies.
...
> drivers/md/Kconfig | 23 ++++++
> drivers/md/Makefile | 2 +-
> drivers/md/dm-verity-target.c | 34 +++++++-
> drivers/md/dm-verity-verify-sig.c | 132 ++++++++++++++++++++++++++++++
> drivers/md/dm-verity-verify-sig.h | 30 +++++++
Please could you also modify Documentation/device-mapper/verity.txt and
describe the new table parameter?
It would be also nice to have a reference example how to configure it,
including how to create the signature file.
Milan
prev parent reply other threads:[~2019-06-08 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 22:31 [RFC PATCH v3 0/1] Add dm verity root hash pkcs7 sig validation Jaskaran Khurana
2019-06-07 22:31 ` [RFC PATCH v3 1/1] " Jaskaran Khurana
2019-06-08 9:11 ` Milan Broz
2019-06-10 21:22 ` Jaskaran Singh Khurana
2019-06-10 23:27 ` Jaskaran Singh Khurana
2019-06-11 5:31 ` James Morris
2019-06-08 8:46 ` Milan Broz [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=3f9f2df1-c811-18d4-2665-0ffddb7a7f0e@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).