From: Jaskaran Khurana <jaskarankhurana@linux.microsoft.com>
To: gmazyland@gmail.com, ebiggers@google.com
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-fsdevel@vger.kernel.org, agk@redhat.com,
snitzer@redhat.com, dm-devel@redhat.com, jmorris@namei.org,
scottsh@microsoft.com, mdsakib@microsoft.com,
mpatocka@redhat.com
Subject: [RFC PATCH v6 0/1] Add dm verity root hash pkcs7 sig validation.
Date: Mon, 1 Jul 2019 11:19:57 -0700 [thread overview]
Message-ID: <20190701181958.6493-1-jaskarankhurana@linux.microsoft.com> (raw)
Changes in v6:
Address comments from Milan Broz and Eric Biggers on v5.
-Keep the verification code under config DM_VERITY_VERIFY_ROOTHASH_SIG.
-Change the command line parameter to requires_signatures(bool) which will
force root hash to be signed and trusted if specified.
-Fix the signature not being present in verity_status. Merged the
https://git.kernel.org/pub/scm/linux/kernel/git/mbroz/linux.git/commit/?h=dm-cryptsetup&id=a26c10806f5257e255b6a436713127e762935ad3
made by Milan Broz and tested it.
Jaskaran Khurana (1):
Add dm verity root hash pkcs7 sig validation.
Documentation/device-mapper/verity.txt | 7 ++
drivers/md/Kconfig | 12 +++
drivers/md/Makefile | 5 +
drivers/md/dm-verity-target.c | 43 +++++++-
drivers/md/dm-verity-verify-sig.c | 133 +++++++++++++++++++++++++
drivers/md/dm-verity-verify-sig.h | 60 +++++++++++
drivers/md/dm-verity.h | 2 +
7 files changed, 257 insertions(+), 5 deletions(-)
create mode 100644 drivers/md/dm-verity-verify-sig.c
create mode 100644 drivers/md/dm-verity-verify-sig.h
--
2.17.1
next reply other threads:[~2019-07-01 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 18:19 Jaskaran Khurana [this message]
2019-07-01 18:19 ` [RFC PATCH v6 1/1] Add dm verity root hash pkcs7 sig validation Jaskaran Khurana
[not found] ` <MN2PR21MB12008A962D4DD8662B3614508AF20@MN2PR21MB1200.namprd21.prod.outlook.com>
2019-07-12 17:33 ` [RFC PATCH v6 0/1] " Jaskaran Singh Khurana
2019-07-16 12:59 ` Milan Broz
2019-07-16 18:08 ` Jaskaran Singh Khurana
2019-07-17 13:08 ` 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=20190701181958.6493-1-jaskarankhurana@linux.microsoft.com \
--to=jaskarankhurana@linux.microsoft.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=gmazyland@gmail.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=mdsakib@microsoft.com \
--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).