[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.2004230234420.12318@namei.org>
Date: Thu, 23 Apr 2020 02:42:49 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: deven.desai@...ux.microsoft.com
cc: agk@...hat.com, axboe@...nel.dk, snitzer@...hat.com,
"Serge E. Hallyn" <serge@...lyn.com>, zohar@...ux.ibm.com,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, dm-devel@...hat.com,
linux-block@...r.kernel.org, jannh@...gle.com,
tyhicks@...ux.microsoft.com, pasha.tatashin@...een.com,
sashal@...nel.org, jaskarankhurana@...ux.microsoft.com,
nramas@...ux.microsoft.com, mdsakib@...ux.microsoft.com,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Stephen Smalley <sds@...ho.nsa.gov>,
Chad Sellers <csellers@...sys.com>,
John Johansen <john.johansen@...onical.com>
Subject: Re: [RFC PATCH v3 05/12] fs: add security blob and hooks for
block_device
On Wed, 15 Apr 2020, deven.desai@...ux.microsoft.com wrote:
> From: Deven Bowers <deven.desai@...ux.microsoft.com>
>
> Add a security blob and associated allocation, deallocation and set hooks
> for a block_device structure.
>
> Signed-off-by: Deven Bowers <deven.desai@...ux.microsoft.com>
Is there any feedback from block or LSM folk on the addition of a security
blob for block_device here?
IPE uses this is to track the status of integrity verification of e.g.
DM-Verity devices, per this code from a subsequent patch:
+ ret = security_bdev_setsecurity(dm_table_get_md(v->ti->table)->bdev,
+ DM_VERITY_SIGNATURE_SEC_NAME,
+ v->sig->sig, v->sig->sig_size);
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists