[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4729647d-3c62-414a-8bce-bb4d3d12a811@infradead.org>
Date: Wed, 6 Mar 2024 16:01:23 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Fan Wu <wufan@...ux.microsoft.com>, corbet@....net, zohar@...ux.ibm.com,
jmorris@...ei.org, serge@...lyn.com, tytso@....edu, ebiggers@...nel.org,
axboe@...nel.dk, agk@...hat.com, snitzer@...nel.org, eparis@...hat.com,
paul@...l-moore.com
Cc: linux-doc@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-fscrypt@...r.kernel.org,
linux-block@...r.kernel.org, dm-devel@...ts.linux.dev,
audit@...r.kernel.org, linux-kernel@...r.kernel.org,
Deven Bowers <deven.desai@...ux.microsoft.com>
Subject: Re: [RFC PATCH v14 14/19] ipe: add support for dm-verity as a trust
provider
On 3/6/24 15:34, Fan Wu wrote:
> +if SECURITY_IPE
> +menu "IPE Trust Providers"
> +
> +config IPE_PROP_DM_VERITY
> + bool "Enable support for dm-verity volumes"
> + depends on DM_VERITY && DM_VERITY_VERIFY_ROOTHASH_SIG
> + help
> + This option enables the properties 'dmverity_signature' and
> + 'dmverity_roothash' in IPE policy. These properties evaluates
evaluate
> + to TRUE when a file is evaluated against a dm-verity volume
> + that was mounted with a signed root-hash or the volume's
> + root hash matches the supplied value in the policy.
--
#Randy
Powered by blists - more mailing lists