From: Ben Whitten <ben.whitten@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RESEND 2/2] fs/squashfs: enable squashfs to generate a verity hashtable
Date: Fri, 23 Mar 2018 18:21:19 +0000 [thread overview]
Message-ID: <1521829279-5156-3-git-send-email-ben.whitten@gmail.com> (raw)
In-Reply-To: <1521829279-5156-1-git-send-email-ben.whitten@gmail.com>
For those times that you want to verify that your readonly filesystem
hasn't been tampered we can generate a dm-verity hash table.
The root hash is enclosed in .table file and must be secured else where.
Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
---
fs/squashfs/Config.in | 6 ++++++
fs/squashfs/squashfs.mk | 10 ++++++++++
2 files changed, 16 insertions(+)
diff --git a/fs/squashfs/Config.in b/fs/squashfs/Config.in
index ca9ddb2..d435249 100644
--- a/fs/squashfs/Config.in
+++ b/fs/squashfs/Config.in
@@ -28,4 +28,10 @@ config BR2_TARGET_ROOTFS_SQUASHFS4_XZ
bool "xz"
endchoice
+
+config BR2_TARGET_ROOTFS_SQUASHFS_VERITY
+ bool "Generate verity hashtable"
+ help
+ As squashfs is readonly it is possible to generate a dm-verity
+ hashtable for use in verified boot systems.
endif
diff --git a/fs/squashfs/squashfs.mk b/fs/squashfs/squashfs.mk
index 51abd5d..8fe09c8 100644
--- a/fs/squashfs/squashfs.mk
+++ b/fs/squashfs/squashfs.mk
@@ -5,6 +5,9 @@
################################################################################
ROOTFS_SQUASHFS_DEPENDENCIES = host-squashfs
+ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS_VERITY),y)
+ROOTFS_SQUASHFS_DEPENDENCIES += host-cryptsetup
+endif
ROOTFS_SQUASHFS_ARGS = -noappend -processors $(PARALLEL_JOBS)
@@ -24,4 +27,11 @@ define ROOTFS_SQUASHFS_CMD
$(HOST_DIR)/bin/mksquashfs $(TARGET_DIR) $@ $(ROOTFS_SQUASHFS_ARGS)
endef
+ifeq ($(BR2_TARGET_ROOTFS_SQUASHFS_VERITY),y)
+define ROOTFS_SQUASHFS_VERITY
+ $(HOST_DIR)/sbin/veritysetup format $@ $@.verity > $@.verity.table
+endef
+ROOTFS_SQUASHFS_POST_GEN_HOOKS += ROOTFS_SQUASHFS_VERITY
+endif
+
$(eval $(rootfs))
--
2.7.4
next prev parent reply other threads:[~2018-03-23 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 18:21 [Buildroot] [PATCH RESEND 0/2] Verified boot tooling Ben Whitten
2018-03-23 18:21 ` [Buildroot] [PATCH RESEND 1/2] fs/ubi: decouple ubi & ubifs Ben Whitten
2018-03-24 3:17 ` Matthew Weber
2018-03-26 21:05 ` Ben Whitten
2018-03-31 9:35 ` Arnout Vandecappelle
2018-03-23 18:21 ` Ben Whitten [this message]
2018-03-31 13:06 ` [Buildroot] [PATCH RESEND 2/2] fs/squashfs: enable squashfs to generate a verity hashtable Peter Korsgaard
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=1521829279-5156-3-git-send-email-ben.whitten@gmail.com \
--to=ben.whitten@gmail.com \
--cc=buildroot@busybox.net \
/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