From: James Morris <jmorris@namei.org>
To: Milan Broz <gmazyland@gmail.com>
Cc: 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, agk@redhat.com,
snitzer@redhat.com, dm-devel@redhat.com, scottsh@microsoft.com,
ebiggers@google.com, Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [RFC PATCH v3 1/1] Add dm verity root hash pkcs7 sig validation
Date: Tue, 11 Jun 2019 15:31:45 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1906111524060.8305@namei.org> (raw)
In-Reply-To: <54170d18-31c7-463d-10b5-9af8b666df0f@gmail.com>
On Sat, 8 Jun 2019, Milan Broz 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.
>
> AFAIK there are tools that use dm-verity internally (some container
> functions in systemd can recognize and check dm-verity partitions) and with
> this option we will just kill possibility to use it without signature.
>
> Anyway, this is up to Mike and Mikulas, I guess generic distros will not
> set this option.
Right, I think this option would not be for a general purpose distro, but
for embedded systems and other cases where the user may want a more
tightly locked-down system.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-06-11 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 22:31 [RFC PATCH v3 0/1] " 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 [this message]
2019-06-08 8:46 ` [RFC PATCH v3 0/1] " 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=alpine.LRH.2.21.1906111524060.8305@namei.org \
--to=jmorris@namei.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=gmazyland@gmail.com \
--cc=jaskarankhurana@linux.microsoft.com \
--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
all inboxes | Powered by JetHome®