From: Mike Snitzer <snitzer@kernel.org>
To: Fan Wu <wufan@linux.microsoft.com>
Cc: corbet@lwn.net, zohar@linux.ibm.com, jmorris@namei.org,
serge@hallyn.com, tytso@mit.edu, ebiggers@kernel.org,
axboe@kernel.dk, agk@redhat.com, eparis@redhat.com,
paul@paul-moore.com, linux-doc@vger.kernel.org,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org,
dm-devel@lists.linux.dev, audit@vger.kernel.org,
linux-kernel@vger.kernel.org,
Deven Bowers <deven.desai@linux.microsoft.com>
Subject: Re: [RFC PATCH v13 14/20] dm verity: consume root hash digest and signature data via LSM hook
Date: Sat, 2 Mar 2024 11:37:20 -0500 [thread overview]
Message-ID: <ZeNVwBkbw2HlMRfa@redhat.com> (raw)
In-Reply-To: <1709168102-7677-15-git-send-email-wufan@linux.microsoft.com>
On Wed, Feb 28 2024 at 7:54P -0500,
Fan Wu <wufan@linux.microsoft.com> wrote:
> From: Deven Bowers <deven.desai@linux.microsoft.com>
>
> dm-verity provides a strong guarantee of a block device's integrity. As
> a generic way to check the integrity of a block device, it provides
> those integrity guarantees to its higher layers, including the filesystem
> level.
>
> An LSM that control access to a resource on the system based on the
> available integrity claims can use this transitive property of
> dm-verity, by querying the underlying block_device of a particular
> file.
>
> The digest and signature information need to be stored in the block
> device to fulfill the next requirement of authorization via LSM policy.
> This will enable the LSM to perform revocation of devices that are still
> mounted, prohibiting execution of files that are no longer authorized
> by the LSM in question.
>
> This patch added two security hook calls in dm-verity to save the
> dm-verity roothash and the roothash signature to the block device's
> LSM blobs. The hook calls are depended on CONFIG_IPE_PROP_DM_VERITY,
> which will be introduced in the next commit.
>
> Signed-off-by: Deven Bowers <deven.desai@linux.microsoft.com>
> Signed-off-by: Fan Wu <wufan@linux.microsoft.com>
> ---
> v2:
> + No Changes
>
> v3:
> + No changes
>
> v4:
> + No changes
>
> v5:
> + No changes
>
> v6:
> + Fix an improper cleanup that can result in
> a leak
>
> v7:
> + Squash patch 08/12, 10/12 to [11/16]
> + Use part0 for block_device, to retrieve the block_device, when
> calling security_bdev_setsecurity
>
> v8:
> + Undo squash of 08/12, 10/12 - separating drivers/md/ from
> security/ & block/
> + Use common-audit function for dmverity_signature.
> + Change implementation for storing the dm-verity digest to use the
> newly introduced dm_verity_digest structure introduced in patch
> 14/20.
> + Create new structure, dm_verity_digest, containing digest algorithm,
> size, and digest itself to pass to the LSM layer. V7 was missing the
> algorithm.
> + Create an associated public header containing this new structure and
> the key values for the LSM hook, specific to dm-verity.
> + Additional information added to commit, discussing the layering of
> the changes and how the information passed will be used.
>
> v9:
> + No changes
>
> v10:
> + No changes
>
> v11:
> + Add an optional field to save signature
> + Move the security hook call to the new finalize hook
>
> v12:
> + No changes
>
> v13:
> + No changes
> ---
> drivers/md/dm-verity-target.c | 71 +++++++++++++++++++++++++++++++++++
> drivers/md/dm-verity.h | 6 +++
> include/linux/dm-verity.h | 19 ++++++++++
> 3 files changed, 96 insertions(+)
> create mode 100644 include/linux/dm-verity.h
>
> diff --git a/drivers/md/dm-verity-target.c b/drivers/md/dm-verity-target.c
> index a99ef30e45ca..e7bc6afae708 100644
> --- a/drivers/md/dm-verity-target.c
> +++ b/drivers/md/dm-verity-target.c
> @@ -13,6 +13,7 @@
> * access behavior.
> */
>
> +#include "dm-core.h"
> #include "dm-verity.h"
> #include "dm-verity-fec.h"
> #include "dm-verity-verify-sig.h"
Why are you including dm-core.h? (DM targets really shouldn't need it).
And from that header:
/*
* DM core internal structures used directly by dm.c, dm-rq.c and dm-table.c.
* DM targets must _not_ deference a mapped_device or dm_table to directly
* access their members!
*/
> @@ -22,6 +23,9 @@
> #include <linux/scatterlist.h>
> #include <linux/string.h>
> #include <linux/jump_label.h>
> +#include <linux/security.h>
> +#include <linux/dm-verity.h>
> +#include <crypto/hash_info.h>
>
> #define DM_MSG_PREFIX "verity"
>
> @@ -990,6 +994,17 @@ static void verity_io_hints(struct dm_target *ti, struct queue_limits *limits)
> blk_limits_io_min(limits, limits->logical_block_size);
> }
>
> +#ifdef CONFIG_IPE_PROP_DM_VERITY
> +static void verity_free_sig(struct dm_verity *v)
> +{
> + kfree(v->root_digest_sig);
> +}
> +#else
> +static inline void verity_free_sig(struct dm_verity *v)
> +{
> +}
> +#endif /* CONFIG_IPE_PROP_DM_VERITY */
> +
> static void verity_dtr(struct dm_target *ti)
> {
> struct dm_verity *v = ti->private;
> @@ -1008,6 +1023,7 @@ static void verity_dtr(struct dm_target *ti)
> kfree(v->salt);
> kfree(v->root_digest);
> kfree(v->zero_digest);
> + verity_free_sig(v);
>
> if (v->tfm)
> crypto_free_ahash(v->tfm);
> @@ -1199,6 +1215,25 @@ static int verity_parse_opt_args(struct dm_arg_set *as, struct dm_verity *v,
> return r;
> }
>
> +#ifdef CONFIG_IPE_PROP_DM_VERITY
> +static int verity_init_sig(struct dm_verity *v, const void *sig,
> + size_t sig_size)
> +{
> + v->sig_size = sig_size;
> + v->root_digest_sig = kmalloc(v->sig_size, GFP_KERNEL);
> + if (!v->root_digest)
> + return -ENOMEM;
> +
> + return 0;
> +}
> +#else
> +static inline int verity_init_sig(struct dm_verity *v, const void *sig,
> + size_t sig_size)
> +{
> + return 0;
> +}
> +#endif /* CONFIG_IPE_PROP_DM_VERITY */
> +
> /*
> * Target parameters:
> * <version> The current format is version 1.
> @@ -1407,6 +1442,13 @@ static int verity_ctr(struct dm_target *ti, unsigned int argc, char **argv)
> ti->error = "Root hash verification failed";
> goto bad;
> }
> +
> + r = verity_init_sig(v, verify_args.sig, verify_args.sig_size);
> + if (r < 0) {
> + ti->error = "Cannot allocate root digest signature";
> + goto bad;
> + }
> +
> v->hash_per_block_bits =
> __fls((1 << v->hash_dev_block_bits) / v->digest_size);
>
> @@ -1557,6 +1599,32 @@ int dm_verity_get_root_digest(struct dm_target *ti, u8 **root_digest, unsigned i
> return 0;
> }
>
> +#ifdef CONFIG_IPE_PROP_DM_VERITY
> +static int verity_finalize(struct dm_target *ti)
> +{
> + struct block_device *bdev;
> + struct dm_verity_digest root_digest;
> + struct dm_verity *v;
> + int r;
> +
> + v = ti->private;
> + bdev = dm_table_get_md(ti->table)->disk->part0;
Must be for dereferencing mapped_device struct here ^
Please remove the dm-core.h include and use this instead:
struct gendisk *disk = dm_disk(dm_table_get_md(ti->table));
Mike
> + root_digest.digest = v->root_digest;
> + root_digest.digest_len = v->digest_size;
> + root_digest.alg = v->alg_name;
> +
> + r = security_bdev_setsecurity(bdev, DM_VERITY_ROOTHASH_SEC_NAME, &root_digest,
> + sizeof(root_digest));
> + if (r)
> + return r;
> +
> + return security_bdev_setsecurity(bdev,
> + DM_VERITY_SIGNATURE_SEC_NAME,
> + v->root_digest_sig,
> + v->sig_size);
> +}
> +#endif /* CONFIG_IPE_PROP_DM_VERITY */
> +
> static struct target_type verity_target = {
> .name = "verity",
> .features = DM_TARGET_SINGLETON | DM_TARGET_IMMUTABLE,
next prev parent reply other threads:[~2024-03-02 16:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 0:54 [RFC PATCH v13 00/20] Integrity Policy Enforcement LSM (IPE) Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 01/20] security: add ipe lsm Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 02/20] ipe: add policy parser Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 03/20] ipe: add evaluation loop Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 04/20] ipe: add LSM hooks on execution and kernel read Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 05/20] initramfs|security: Add a security hook to do_populate_rootfs() Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 06/20] ipe: introduce 'boot_verified' as a trust provider Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 07/20] security: add new securityfs delete function Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 08/20] ipe: add userspace interface Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 09/20] uapi|audit|ipe: add ipe auditing support Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 10/20] ipe: add permissive toggle Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 11/20] block|security: add LSM blob to block_device Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 12/20] dm verity: set DM_TARGET_SINGLETON feature flag Fan Wu
2024-03-02 16:01 ` Mike Snitzer
2024-02-29 0:54 ` [RFC PATCH v13 13/20] dm: add finalize hook to target_type Fan Wu
2024-03-02 16:13 ` Mike Snitzer
2024-02-29 0:54 ` [RFC PATCH v13 14/20] dm verity: consume root hash digest and signature data via LSM hook Fan Wu
2024-03-02 16:22 ` Mike Snitzer
2024-03-02 16:37 ` Mike Snitzer [this message]
2024-02-29 0:54 ` [RFC PATCH v13 15/20] ipe: add support for dm-verity as a trust provider Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 16/20] fsverity: consume builtin signature via LSM hook Fan Wu
2024-02-29 0:54 ` [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider Fan Wu
2024-02-29 4:01 ` Randy Dunlap
2024-02-29 4:46 ` Eric Biggers
2024-02-29 18:59 ` Fan Wu
2024-02-29 19:42 ` Eric Biggers
2024-02-29 19:59 ` Fan Wu
2024-02-29 0:55 ` [RFC PATCH v13 18/20] scripts: add boot policy generation program Fan Wu
2024-02-29 0:55 ` [RFC PATCH v13 19/20] ipe: kunit test for parser Fan Wu
2024-02-29 0:55 ` [RFC PATCH v13 20/20] documentation: add ipe documentation Fan Wu
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=ZeNVwBkbw2HlMRfa@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=audit@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=deven.desai@linux.microsoft.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=tytso@mit.edu \
--cc=wufan@linux.microsoft.com \
--cc=zohar@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).