heads/modules/cryptsetup

modules-$(CONFIG_CRYPTSETUP) += cryptsetup

cryptsetup_depends := util-linux popt lvm2 json-c $(musl_dep)

cryptsetup_version := 2.3.3
cryptsetup_dir := cryptsetup-$(cryptsetup_version)
cryptsetup_tar := cryptsetup-$(cryptsetup_version).tar.xz
cryptsetup_url := https://www.kernel.org/pub/linux/utils/cryptsetup/v2.3/cryptsetup-$(cryptsetup_version).tar.xz
cryptsetup_hash := 3bca4ffe39e2f94cef50f6ea65acb873a6dbce5db34fc6bcefe38b6d095e82df

# Use an empty prefix so that the executables will not include the
# build path.
cryptsetup_configure := ./configure \
	$(CROSS_TOOLS) \
	--host i386-elf-linux \
	--prefix "/" \
	--disable-rpath \
	--disable-gcrypt-pbkdf2 \
	--enable-cryptsetup-reencrypt \
	--with-crypto_backend=kernel \
	--with-tmpfilesdir=$(INSTALL)/lib/tmpfiles.d

# but after building, replace prefix so that they will be installed
# in the correct directory.
cryptsetup_target := \
	$(MAKE_JOBS) \
	&& $(MAKE) \
		-C $(build)/$(cryptsetup_dir) \
		prefix="$(INSTALL)" \
		install

cryptsetup_output := \
	.libs/cryptsetup \
	.libs/cryptsetup-reencrypt \
	.libs/veritysetup \

cryptsetup_libraries := \
	.libs/libcryptsetup.so.12 \
Build time configuration for startup scripts and modules. This addresses multiple issues: * Issue #63: initrd is build fresh each time, so tracked files do not matter. * Issue #144: build time configuration * Issue #123: allows us to customize the startup experience * Issue #122: manual start-xen will go away * Issue #25: tpmtotp PCRs are updated after reading the secret * Issue #16: insmod now meaures modules 2017-03-31 15:18:46 +00:00			`modules-$(CONFIG_CRYPTSETUP) += cryptsetup`
cryptsetup for dm-verity support 2016-08-19 15:20:41 +00:00
Separate json-c module from cryptsetup module 2020-06-23 09:03:17 +00:00			`cryptsetup_depends := util-linux popt lvm2 json-c $(musl_dep)`
Download and build almost all dependencies. As part of issue #1, we should build all libraries and programs that we deploy into the Heads initrd. This modifies the module configurations for all of them to install into heads/install so that we can build against them. Add dmsetup, cryptsetup and veritysetup (issue #46). Build gpgv 1.4 as a standalone tool (issue #23). Modify populate-lib to use the install directory by setting LD_LIBRARY_PATH (issue #35). 2016-12-28 17:45:12 +00:00
Upgrade cryptsetup to version 2.3.3 2020-06-10 08:24:03 +00:00			`cryptsetup_version := 2.3.3`
cryptsetup for dm-verity support 2016-08-19 15:20:41 +00:00			`cryptsetup_dir := cryptsetup-$(cryptsetup_version)`
			`cryptsetup_tar := cryptsetup-$(cryptsetup_version).tar.xz`
Upgrade cryptsetup to version 2.3.3 2020-06-10 08:24:03 +00:00			`cryptsetup_url := https://www.kernel.org/pub/linux/utils/cryptsetup/v2.3/cryptsetup-$(cryptsetup_version).tar.xz`
			`cryptsetup_hash := 3bca4ffe39e2f94cef50f6ea65acb873a6dbce5db34fc6bcefe38b6d095e82df`
cryptsetup for dm-verity support 2016-08-19 15:20:41 +00:00
Make modules not depend on build path (issue #1). Use --prefix="" to ensure that no destination paths are in libraries. Use -fdebug-prefix-map to rewrite build path so that it does not appear in the executables. Use -gno-record-gcc-switches to ensure that the -fdebug-prefix-map does not appear in the executables. 2017-01-28 18:14:56 +00:00			`# Use an empty prefix so that the executables will not include the`
			`# build path.`
Update cryptsetup module and strip it down Signed-off-by: Philipp Deppenwiese <zaolin@das-labor.org> 2016-11-29 19:24:01 +00:00			`cryptsetup_configure := ./configure \`
Define $(CROSS_TOOLS) to ensure reproducible builds (issue #173) Each of the submodule configuration files defined a subset of the cross compiler tools that it used and many were picking up the system `ar`, `nm`, `strip, `ld`, etc. They all now use a `Makefile` macro that defines the path to the proper cross compiler tools. For ones that need the tools, but not the musl-libc gcc, there is $(CROSS_TOOLS_NOCC) that is all of them without gcc. This is for musl-libc itself, as well as xen and the Linux kernel. 2017-04-08 17:23:34 +00:00			`$(CROSS_TOOLS) \`
Working build with musl-libc cross compiler (issue #77). Pass in the --host argument to all of the various programs that need to treat the configure scripts as cross compilation targets. This removes all dependencies on the host libc (issue #7) and adds some tools to the initrd (cryptsetup #46). 2017-01-04 21:39:10 +00:00			`--host i386-elf-linux \`
prefix should not be empty 2017-04-07 13:51:15 +00:00			`--prefix "/" \`
[WIP] cross build json-c and cryptsetup 2020-10-22 11:16:00 +00:00			`--disable-rpath \`
Fix build issue * use --libdir to fix issue with .la files which had //lib as lib folder * add libblkid as library 2020-06-16 08:29:01 +00:00			`--disable-gcrypt-pbkdf2 \`
			`--enable-cryptsetup-reencrypt \`
Build cryptsetup and install it into the initrd 2016-12-01 19:03:55 +00:00			`--with-crypto_backend=kernel \`
[WIP] cross build json-c and cryptsetup 2020-10-22 11:16:00 +00:00			`--with-tmpfilesdir=$(INSTALL)/lib/tmpfiles.d`
Build cryptsetup and install it into the initrd 2016-12-01 19:03:55 +00:00
Make modules not depend on build path (issue #1). Use --prefix="" to ensure that no destination paths are in libraries. Use -fdebug-prefix-map to rewrite build path so that it does not appear in the executables. Use -gno-record-gcc-switches to ensure that the -fdebug-prefix-map does not appear in the executables. 2017-01-28 18:14:56 +00:00			`# but after building, replace prefix so that they will be installed`
			`# in the correct directory.`
Working build with musl-libc cross compiler (issue #77). Pass in the --host argument to all of the various programs that need to treat the configure scripts as cross compilation targets. This removes all dependencies on the host libc (issue #7) and adds some tools to the initrd (cryptsetup #46). 2017-01-04 21:39:10 +00:00			`cryptsetup_target := \`
Separate json-c module from cryptsetup module 2020-06-23 09:03:17 +00:00			`$(MAKE_JOBS) \`
			`&& $(MAKE) \`
			`-C $(build)/$(cryptsetup_dir) \`
			`prefix="$(INSTALL)" \`
			`install`
Download and build almost all dependencies. As part of issue #1, we should build all libraries and programs that we deploy into the Heads initrd. This modifies the module configurations for all of them to install into heads/install so that we can build against them. Add dmsetup, cryptsetup and veritysetup (issue #46). Build gpgv 1.4 as a standalone tool (issue #23). Modify populate-lib to use the install directory by setting LD_LIBRARY_PATH (issue #35). 2016-12-28 17:45:12 +00:00
Build cryptsetup and install it into the initrd 2016-12-01 19:03:55 +00:00			`cryptsetup_output := \`
[WIP] cross build json-c and cryptsetup 2020-10-22 11:16:00 +00:00			`.libs/cryptsetup \`
			`.libs/cryptsetup-reencrypt \`
			`.libs/veritysetup \`
Build cryptsetup and install it into the initrd 2016-12-01 19:03:55 +00:00
Remove populate-lib, rework libraries and kernel module installation. The populate-lib program was buggy on some systems and could accidentally introduce unwanted libraries into the initrd. The Makefile now uses the modules' $(module_libraries) variable to select which libraries should be installed into the initrd. Kernel modules are now stripped and installed using a similar system. 2017-03-29 19:15:03 +00:00			`cryptsetup_libraries := \`
[WIP] cross build json-c and cryptsetup 2020-10-22 11:16:00 +00:00			`.libs/libcryptsetup.so.12 \`
Download and build almost all dependencies. As part of issue #1, we should build all libraries and programs that we deploy into the Heads initrd. This modifies the module configurations for all of them to install into heads/install so that we can build against them. Add dmsetup, cryptsetup and veritysetup (issue #46). Build gpgv 1.4 as a standalone tool (issue #23). Modify populate-lib to use the install directory by setting LD_LIBRARY_PATH (issue #35). 2016-12-28 17:45:12 +00:00