man/systemd-veritysetup-generator.xml

   1 <?xml version="1.0"?>
   2 <!--*-nxml-*-->
   3 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
   4 <!--
   5   SPDX-License-Identifier: LGPL-2.1+
   6
   7   Copyright 2016 Lennart Poettering
   8 -->
   9 <refentry id="systemd-veritysetup-generator" conditional='HAVE_LIBCRYPTSETUP'>
  10
  11   <refentryinfo>
  12     <title>systemd-veritysetup-generator</title>
  13     <productname>systemd</productname>
  14
  15     <authorgroup>
  16       <author>
  17         <contrib>Developer</contrib>
  18         <firstname>Lennart</firstname>
  19         <surname>Poettering</surname>
  20         <email>lennart@poettering.net</email>
  21       </author>
  22     </authorgroup>
  23   </refentryinfo>
  24
  25   <refmeta>
  26     <refentrytitle>systemd-veritysetup-generator</refentrytitle>
  27     <manvolnum>8</manvolnum>
  28   </refmeta>
  29
  30   <refnamediv>
  31     <refname>systemd-veritysetup-generator</refname>
  32     <refpurpose>Unit generator for integrity protected block devices</refpurpose>
  33   </refnamediv>
  34
  35   <refsynopsisdiv>
  36     <para><filename>/usr/lib/systemd/system-generators/systemd-veritysetup-generator</filename></para>
  37   </refsynopsisdiv>
  38
  39   <refsect1>
  40     <title>Description</title>
  41
  42     <para><filename>systemd-veritysetup-generator</filename> is a generator that translates kernel command line options
  43     configuring integrity protected block devices (verity) into native systemd units early at boot and when
  44     configuration of the system manager is reloaded. This will create
  45     <citerefentry><refentrytitle>systemd-veritysetup@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
  46     units as necessary.</para>
  47
  48     <para>Currently, only a single verity device may be se up with this generator, backing the root file system of the
  49     OS.</para>
  50
  51     <para><filename>systemd-veritysetup-generator</filename> implements
  52     <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
  53   </refsect1>
  54
  55   <refsect1>
  56     <title>Kernel Command Line</title>
  57
  58     <para><filename>systemd-veritysetup-generator</filename>
  59     understands the following kernel command line parameters:</para>
  60
  61     <variablelist class='kernel-commandline-options'>
  62       <varlistentry>
  63         <term><varname>systemd.verity=</varname></term>
  64         <term><varname>rd.systemd.verity=</varname></term>
  65
  66         <listitem><para>Takes a boolean argument. Defaults to <literal>yes</literal>. If <literal>no</literal>,
  67         disables the generator entirely. <varname>rd.systemd.verity=</varname> is honored only by the initial RAM disk
  68         (initrd) while <varname>systemd.verity=</varname> is honored by both the host system and the
  69         initrd. </para></listitem>
  70       </varlistentry>
  71
  72       <varlistentry>
  73         <term><varname>roothash=</varname></term>
  74
  75         <listitem><para>Takes a root hash value for the root file system. Expects a hash value formatted in hexadecimal
  76         characters, of the appropriate length (i.e. most likely 256 bit/64 characters, or longer). If not specified via
  77         <varname>systemd.verity_root_data=</varname> and <varname>systemd.verity_root_hash=</varname>, the hash and
  78         data devices to use are automatically derived from the specified hash value. Specifically, the data partition
  79         device is looked for under a GPT partition UUID derived from the first 128bit of the root hash, the hash
  80         partition device is looked for under a GPT partition UUID derived from the last 128bit of the root hash. Hence
  81         it is usually sufficient to specify the root hash to boot from an integrity protected root file system, as
  82         device paths are automatically determined from it — as long as the partition table is properly set up.</para>
  83         </listitem>
  84       </varlistentry>
  85
  86       <varlistentry>
  87         <term><varname>systemd.verity_root_data=</varname></term>
  88         <term><varname>systemd.verity_root_hash=</varname></term>
  89
  90         <listitem><para>These two settings take block device paths as arguments, and may be use to explicitly configure
  91         the data partition and hash partition to use for setting up the integrity protection for the root file
  92         system. If not specified, these paths are automatically derived from the <varname>roothash=</varname> argument
  93         (see above).</para></listitem>
  94       </varlistentry>
  95
  96     </variablelist>
  97   </refsect1>
  98
  99   <refsect1>
 100     <title>See Also</title>
 101     <para>
 102       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 103       <citerefentry><refentrytitle>systemd-veritysetup@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 104       <citerefentry project='die-net'><refentrytitle>veritysetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 105       <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 106     </para>
 107   </refsect1>
 108
 109 </refentry>