1SYSTEMD-VERITYSETUP-GENERAsTyOsRt(e8m)d-veritysetup-geSnYeSrTaEtMoDr-VERITYSETUP-GENERATOR(8)
2
3
4

NAME

6       systemd-veritysetup-generator - Unit generator for verity protected
7       block devices
8

SYNOPSIS

10       /usr/lib/systemd/system-generators/systemd-veritysetup-generator
11

DESCRIPTION

13       systemd-veritysetup-generator is a generator that translates kernel
14       command line options configuring verity protected block devices into
15       native systemd units early at boot and when configuration of the system
16       manager is reloaded. This will create systemd-veritysetup@.service(8)
17       units as necessary.
18
19       Currently, only two verity devices may be set up with this generator,
20       backing the root and /usr file systems of the OS.
21
22       systemd-veritysetup-generator implements systemd.generator(7).
23

KERNEL COMMAND LINE

25       systemd-veritysetup-generator understands the following kernel command
26       line parameters:
27
28       systemd.verity=, rd.systemd.verity=
29           Takes a boolean argument. Defaults to "yes". If "no", disables the
30           generator entirely.  rd.systemd.verity= is honored only by the
31           initrd while systemd.verity= is honored by both the host system and
32           the initrd.
33
34       roothash=
35           Takes a root hash value for the root file system. Expects a hash
36           value formatted in hexadecimal characters of the appropriate length
37           (i.e. most likely 256 bit/64 characters, or longer). If not
38           specified via systemd.verity_root_data= and
39           systemd.verity_root_hash=, the hash and data devices to use are
40           automatically derived from the specified hash value. Specifically,
41           the data partition device is looked for under a GPT partition UUID
42           derived from the first 128-bit of the root hash, the hash partition
43           device is looked for under a GPT partition UUID derived from the
44           last 128-bit of the root hash. Hence it is usually sufficient to
45           specify the root hash to boot from a verity protected root file
46           system, as device paths are automatically determined from it — as
47           long as the partition table is properly set up.
48
49       systemd.verity_root_data=, systemd.verity_root_hash=
50           These two settings take block device paths as arguments and may be
51           used to explicitly configure the data partition and hash partition
52           to use for setting up the verity protection for the root file
53           system. If not specified, these paths are automatically derived
54           from the roothash= argument (see above).
55
56       systemd.verity_root_options=
57           Takes a comma-separated list of dm-verity options. Expects the
58           following options superblock=BOOLEAN, format=NUMBER,
59           data-block-size=BYTES, hash-block-size=BYTES, data-blocks=BLOCKS,
60           hash-offset=BYTES, salt=HEX, uuid=UUID, ignore-corruption,
61           restart-on-corruption, ignore-zero-blocks, check-at-most-once,
62           panic-on-corruption, hash=HASH, fec-device=PATH, fec-offset=BYTES,
63           fec-roots=NUM and root-hash-signature=PATH|base64:HEX. See
64           veritysetup(8) for more details.
65
66       usrhash=, systemd.verity_usr_data=, systemd.verity_usr_hash=,
67       systemd.verity_usr_options=
68           Equivalent to their counterparts for the root file system as
69           described above, but apply to the /usr/ file system instead.
70

SEE ALSO

72       systemd(1), systemd-veritysetup@.service(8), veritysetup(8), systemd-
73       fstab-generator(8)
74
75
76
77systemd 254                                   SYSTEMD-VERITYSETUP-GENERATOR(8)
Impressum