3 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
4 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
5 <!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
6 <refentry id=
"systemd-pcrlock" conditional='ENABLE_BOOTLOADER HAVE_OPENSSL HAVE_TPM2'
7 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
10 <title>systemd-pcrlock
</title>
11 <productname>systemd
</productname>
15 <refentrytitle>systemd-pcrlock
</refentrytitle>
16 <manvolnum>8</manvolnum>
20 <refname>systemd-pcrlock
</refname>
21 <refname>systemd-pcrlock-file-system.service
</refname>
22 <refname>systemd-pcrlock-firmware-code.service
</refname>
23 <refname>systemd-pcrlock-firmware-config.service
</refname>
24 <refname>systemd-pcrlock-machine-id.service
</refname>
25 <refname>systemd-pcrlock-make-policy.service
</refname>
26 <refname>systemd-pcrlock-secureboot-authority.service
</refname>
27 <refname>systemd-pcrlock-secureboot-policy.service
</refname>
28 <refpurpose>Analyze and predict TPM2 PCR states and generate an access policy from the prediction
</refpurpose>
33 <command>/usr/lib/systemd/systemd-pcrlock
</command> <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg>
38 <title>Description
</title>
40 <para>Note: this command is experimental for now. While it is likely to become a regular component of
41 systemd, it might still change in behaviour and interface.
</para>
43 <para><command>systemd-pcrlock
</command> is a tool that may be used to analyze and predict TPM2 PCR
44 measurements, and generate TPM2 access policies from the prediction which it stores in a TPM2 NV index
45 (i.e. in the TPM2 non-volatile memory). This may then be used to restrict access to TPM2 objects (such as
46 disk encryption keys) to system boot-ups in which only specific, trusted components are used.
</para>
48 <para><command>systemd-pcrlock
</command> uses as input for its analysis and prediction:
</para>
51 <listitem><para>The UEFI firmware TPM2 event log
52 (i.e.
<filename>/sys/kernel/security/tpm0/binary_bios_measurements
</filename>) of the current
53 boot.
</para></listitem>
55 <listitem><para>The userspace TPM2 event log
56 (i.e.
<filename>/run/log/systemd/tpm2-measure.log
</filename>) of the current
57 boot.
</para></listitem>
59 <listitem><para>The current PCR state of the TPM2 chip.
</para></listitem>
61 <listitem><para>Boot component definition files (
<filename>*.pcrlock
</filename> and
62 <filename>*.pcrlock.d/*.pcrlock
</filename>, see
63 <citerefentry><refentrytitle>systemd.pcrlock
</refentrytitle><manvolnum>5</manvolnum></citerefentry>)
64 that each define expected measurements for one component of the boot process, permitting alternative
65 variants for each. (Variants may be used used to bless multiple kernel versions or boot loader versions
66 at the same time.)
</para></listitem>
69 <para>It uses these inputs to generate a combined event log, validating it against the PCR states. It
70 then attempts to recognize event log records and matches them against the defined components. For each PCR
71 where this can be done comprehensively (i.e. where all listed records and all defined components have
72 been matched) this may then be used to predict future PCR measurements, taking the alternative variants
73 defined for each component into account. This prediction may then be converted into a TPM2 access policy
74 (consisting of TPM2
<function>PolicyPCR
</function> and
<function>PolicyOR
</function> items), which is
75 then stored in an NV index in the TPM2. This may be used to then lock secrets (such as disk encryption
76 keys) to these policies (via a TPM2
<function>PolicyAuthorizeNV
</function> policy).
</para>
78 <para>Use tools such as
79 <citerefentry><refentrytitle>systemd-cryptenroll
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
80 or
<citerefentry><refentrytitle>systemd-repart
</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
81 bind disk encryption to such a
<command>systemd-pcrlock
</command> TPM2 policy. Specifically, see the
82 <option>--tpm2-pcrlock=
</option> switches of these tools.
</para>
84 <para>The access policy logic requires a TPM2 device that implements the
85 <literal>PolicyAuthorizeNV
</literal> command, i.e. implements TPM
2.0 version
1.38 or newer.
</para>
89 <title>Commands
</title>
91 <para>The following commands are understood:
</para>
95 <term><command>log
</command></term>
97 <listitem><para>This reads the combined TPM2 event log, validates it, matches it against the current
98 PCR values, and outputs both in tabular form. Combine with
<option>--json=
</option> to generate
99 output in JSON format.
</para>
101 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
105 <term><command>cel
</command></term>
107 <listitem><para>This reads the combined TPM2 event log and writes it to STDOUT in
<ulink
108 url=
"https://trustedcomputinggroup.org/resource/canonical-event-log-format/">TCG Common Event Log
109 Format (CEL-JSON)
</ulink> format.
</para>
111 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
115 <term><command>list-components
</command></term>
117 <listitem><para>Shows a list of component definitions and their variants, i.e. the
118 <filename>*.pcrlock
</filename> files discovered in
<filename>/var/lib/pcrlock.d/
</filename>,
119 <filename>/usr/lib/pcrlock.d/
</filename>, and the other supported directories. See
120 <citerefentry><refentrytitle>systemd.pcrlock
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
121 for details on these files and the full list of directories searched.
</para>
123 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
127 <term><command>predict
</command></term>
129 <listitem><para>Predicts the PCR state on future boots. This will analyze the TPM2 event log as
130 described above, recognize components, and then generate all possible resulting PCR values for all
131 combinations of component variants. Note that no prediction is made for PCRs whose value does not
132 match the event log records, for which unrecognized measurements are discovered or for which
133 components are defined that cannot be found in the event log. This is a safety measure to ensure that
134 any generated access policy can be fulfilled correctly on current and future boots.
</para>
136 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
141 <term><command>make-policy
</command></term>
143 <listitem><para>This predicts the PCR state for future boots, much like the
144 <command>predict
</command> command above. It then uses this data to generate a TPM2 access policy
145 which it stores in a TPM2 NV index. The prediction and information about the used TPM2 and its NV
146 index are written to
<filename>/var/lib/systemd/pcrlock.json
</filename>.
</para>
148 <para>The NV index is allocated on first invocation, and updated on subsequent invocations.
</para>
150 <para>The NV index contents may be changed (and thus the policy stored in it updated) by providing an
151 access PIN. This PIN is normally generated automatically and stored in encrypted form (with an access
152 policy binding it to the NV index itself) in the aforementioned JSON policy file. This PIN may be
153 chosen by the user, via the
<option>--recovery-pin=
</option> switch. If specified it may be used as
154 alternative path of access to update the policy.
</para>
156 <para>If the new prediction matches the old this command terminates quickly and executes no further
157 operation. (Unless
<option>--force
</option> is specified, see below.)
</para>
159 <para>Starting with v256, a copy of the
<filename>/var/lib/systemd/pcrlock.json
</filename> policy
160 file is encoded in a credential (see
161 <citerefentry><refentrytitle>systemd-creds
</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
162 details) and written to the EFI System Partition or XBOOTLDR partition, in the
163 <filename>/loader/credentials/
</filename> subdirectory. There it is picked up at boot by
164 <citerefentry><refentrytitle>systemd-stub
</refentrytitle><manvolnum>7</manvolnum></citerefentry> and
165 passed to the invoked initrd, where it can be used to unlock the root file system (which typically
166 contains
<filename>/var/
</filename>, which is where the primary copy of the policy is located, which
167 hence cannot be used to unlock the root file system). The credential file is named after the boot
168 entry token of the installation (see
169 <citerefentry><refentrytitle>bootctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>), which
170 is configurable via the
<option>--entry-token=
</option> switch, see below.
</para>
172 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
177 <term><command>remove-policy
</command></term>
179 <listitem><para>Removes a previously generated policy. Deletes the
180 <filename>/var/lib/systemd/pcrlock.json
</filename> file, and deallocates the NV index.
</para>
182 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
187 <term><command>lock-firmware-code
</command></term>
188 <term><command>unlock-firmware-code
</command></term>
190 <listitem><para>Generates/removes
<filename>.pcrlock
</filename> files based on the TPM2 event log of
191 the current boot covering all records for PCRs
0 (
"platform-code") and
2 (
"external-code").
</para>
193 <para>This operation allows locking the boot process to the current version of the firmware of the
194 system and its extension cards. This operation should only be used if the system vendor does not
195 provide suitable pcrlock data ahead of time.
</para>
197 <para>Note that this data only matches the current version of the firmware. If a firmware update is
198 applied this data will be out-of-date and any access policy generated from it will no longer pass. It
199 is thus recommended to invoke
<command>unlock-firmware-code
</command> before doing a firmware update,
200 followed by
<command>make-policy
</command> to refresh the policy.
</para>
202 <para><command>systemd-pcrlock lock-firmware-code
</command> is invoked automatically at boot via the
203 <filename>systemd-pcrlock-firmware-code.service
</filename> unit, if enabled. This ensures that an
204 access policy managed by
<command>systemd-pcrlock
</command> is automatically locked to the new
205 firmware version whenever the policy has been relaxed temporarily, in order to cover for firmware
206 updates, as described above.
</para>
208 <para>The files are only generated from the event log if the event log matches the current TPM2 PCR
211 <para>This writes/removes the files
212 <filename>/var/lib/pcrlock.d/
250-firmware-code-early.pcrlock.d/generated.pcrlock
</filename> and
213 <filename>/var/lib/pcrlock.d/
550-firmware-code-late.pcrlock.d/generated.pcrlock
</filename>.
</para>
215 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
220 <term><command>lock-firmware-config
</command></term>
221 <term><command>unlock-firmware-config
</command></term>
223 <listitem><para>This is similar to
224 <command>lock-firmware-code
</command>/
<command>unlock-firmware-code
</command> but locks down the
225 firmware configuration, i.e. PCRs
1 (
"platform-config") and
3 (
"external-config").
</para>
227 <para>This functionality should be used with care as in most scenarios a minor firmware configuration
228 change should not invalidate access policies to TPM2 objects. Also note that some systems measure
229 unstable and unpredictable information (e.g. current CPU voltages, temperatures, as part of SMBIOS
230 data) to these PCRs, which means this form of lockdown cannot be used reliably on such systems. Use
231 this functionality only if the system and hardware is well known and does not suffer by these
232 limitations, for example in virtualized environments.
</para>
234 <para>Use
<command>unlock-firmware-config
</command> before making firmware configuration changes. If
235 the
<filename>systemd-pcrlock-firmware-config.service
</filename> unit is enabled it will
236 automatically generate a pcrlock file from the new measurements.
</para>
238 <para>This writes/removes the files
239 <filename>/var/lib/pcrlock.d/
250-firmware-config-early.pcrlock.d/generated.pcrlock
</filename> and
240 <filename>/var/lib/pcrlock.d/
550-firmware-config-late.pcrlock.d/generated.pcrlock
</filename>.
</para>
242 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
247 <term><command>lock-secureboot-policy
</command></term>
248 <term><command>unlock-secureboot-policy
</command></term>
250 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on the SecureBoot policy
251 currently enforced. This looks at the SecureBoot, PK, KEK, db, dbx, dbt, dbr EFI variables and
252 predicts their measurements to PCR
7 (
"secure-boot-policy") on the next boot.
</para>
254 <para>Use
<command>unlock-firmware-config
</command> before applying SecureBoot policy updates. If
255 the
<filename>systemd-pcrlock-secureboot-policy.service
</filename> unit is enabled it will
256 automatically generate a pcrlock file from the policy discovered.
</para>
258 <para>This writes/removes the file
259 <filename>/var/lib/pcrlock.d/
230-secureboot-policy.pcrlock.d/generated.pcrlock
</filename>.
</para>
261 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
266 <term><command>lock-secureboot-authority
</command></term>
267 <term><command>unlock-secureboot-authority
</command></term>
269 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on the SecureBoot
270 authorities used to validate the boot path. SecureBoot authorities are the specific SecureBoot
271 database entries that where used to validate the UEFI PE binaries executed at boot. This looks at the
272 event log of the current boot, and uses relevant measurements on PCR
7
273 (
"secure-boot-policy").
</para>
275 <para>This writes/removes the file
276 <filename>/var/lib/pcrlock.d/
620-secureboot-authority.pcrlock.d/generated.pcrlock
</filename>.
</para>
278 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
283 <term><command>lock-gpt
</command> <optional><replaceable>DEVICE
</replaceable></optional></term>
284 <term><command>unlock-gpt
</command></term>
286 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on the GPT partition
287 table of the specified disk. If no disk is specified automatically determines the block device
288 backing the root file system. This locks the state of the disk partitioning of the booted medium,
289 which firmware measures to PCR
5 (
"boot-loader-config").
</para>
291 <para>This writes/removes the file
292 <filename>/var/lib/pcrlock.d/
600-gpt.pcrlock.d/generated.pcrlock
</filename>.
</para>
294 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
299 <term><command>lock-pe
</command> <optional><replaceable>BINARY
</replaceable></optional></term>
300 <term><command>unlock-pe
</command></term>
302 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on the specified PE
303 binary. This is useful for predicting measurements the firmware makes to PCR
4 (
"boot-loader-code")
304 if the specified binary is part of the UEFI boot process. Use this on boot loader binaries and
305 suchlike. Use
<command>lock-uki
</command> (see below) for PE binaries that are unified kernel images
308 <para>Expects a path to the PE binary as argument. If not specified, reads the binary from STDIN
311 <para>The pcrlock file to write must be specified via the
<option>--pcrlock=
</option> switch.
</para>
313 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
318 <term><command>lock-uki
</command> <optional><replaceable>UKI
</replaceable></optional></term>
319 <term><command>unlock-uki
</command></term>
321 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on the specified UKI PE
322 binary. This is useful for predicting measurements the firmware makes to PCR
4 (
"boot-loader-code"),
323 and
<citerefentry><refentrytitle>systemd-stub
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
324 makes to PCR
11 (
"kernel-boot"), if the specified UKI is booted. This is a superset of
325 <command>lock-pe
</command>.
</para>
327 <para>Expects a path to the UKI PE binary as argument. If not specified, reads the binary from STDIN
330 <para>The pcrlock file to write must be specified via the
<option>--pcrlock=
</option> switch.
</para>
332 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
337 <term><command>lock-machine-id
</command></term>
338 <term><command>unlock-machine-id
</command></term>
340 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on
341 <filename>/etc/machine-id
</filename>. This is useful for predicting measurements
342 <citerefentry><refentrytitle>systemd-pcrmachine.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
343 makes to PCR
15 (
"system-identity").
</para>
345 <para>This writes/removes the file
346 <filename>/var/lib/pcrlock.d/
820-machine-id.pcrlock
</filename>.
</para>
348 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
353 <term><command>lock-file-system
</command> <optional><replaceable>PATH
</replaceable></optional></term>
354 <term><command>unlock-file-system
</command> <optional><replaceable>PATH
</replaceable></optional></term>
356 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on file system
357 identity. This is useful for predicting measurements
358 <citerefentry><refentrytitle>systemd-pcrfs@.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
359 makes to PCR
15 (
"system-identity") for the root and
<filename>/var/
</filename> file systems.
</para>
361 <para>This writes/removes the files
362 <filename>/var/lib/pcrlock.d/
830-root-file-system.pcrlock
</filename> and
363 <filename>/var/lib/pcrlock.d/
840-file-system-
<replaceable>path
</replaceable>.pcrlock
</filename>.
</para>
365 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
370 <term><command>lock-kernel-cmdline
</command> <optional><replaceable>FILE
</replaceable></optional></term>
371 <term><command>unlock-kernel-cmdline
</command></term>
373 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on
374 <filename>/proc/cmdline
</filename> (or the specified file if given). This is useful for predicting
375 measurements the Linux kernel makes to PCR
9 (
"kernel-initrd").
</para>
377 <para>This writes/removes the file
378 <filename>/var/lib/pcrlock.d/
710-kernel-cmdline.pcrlock/generated.pcrlock
</filename>.
</para>
380 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
385 <term><command>lock-kernel-initrd
</command> <replaceable>FILE
</replaceable></term>
386 <term><command>unlock-kernel-initrd
</command></term>
388 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on a kernel initrd cpio
389 archive. This is useful for predicting measurements the Linux kernel makes to PCR
9
390 (
"kernel-initrd"). Do not use for
<command>systemd-stub
</command> UKIs, as the initrd is combined
391 dynamically from various sources and hence does not take a single input, like this command.
</para>
393 <para>This writes/removes the file
394 <filename>/var/lib/pcrlock.d/
720-kernel-initrd.pcrlock/generated.pcrlock
</filename>.
</para>
396 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
401 <term><command>lock-raw
</command> <optional><replaceable>FILE
</replaceable></optional></term>
402 <term><command>unlock-raw
</command></term>
404 <listitem><para>Generates/removes a
<filename>.pcrlock
</filename> file based on raw binary data. The
405 data is either read from the specified file or from STDIN (if none is specified). This requires that
406 <option>--pcrs=
</option> is specified. The generated .pcrlock file is written to the file specified
407 via
<option>--pcrlock=
</option> or to STDOUT (if none is specified).
</para>
409 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
417 <title>Options
</title>
419 <para>The following options are understood:
</para>
423 <term><option>--raw-description
</option></term>
425 <listitem><para>When displaying the TPM2 event log do not attempt to decode the records to provide a
426 friendly event log description string. Instead, show the binary payload data in escaped form.
</para>
428 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
432 <term><option>--pcr=
</option></term>
434 <listitem><para>Specifies the PCR number to use. May be specified more than once to select multiple
437 <para>This is used by
<command>lock-raw
</command> and
<command>lock-pe
</command> to select the
438 PCR to lock against.
</para>
440 <para>If used with
<command>predict
</command> and
<command>make-policy
</command> this will override
441 which PCRs to include in the prediction and policy. If unspecified this defaults to PCRs
0-
5,
7,
442 11-
15. Note that these commands will not include any PCRs in the prediction/policy (even if specified
443 explicitly) if there are measurements in the event log that do not match the current PCR value, or
444 there are unrecognized measurements in the event log, or components define measurements not seen in
445 the event log.
</para>
447 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
451 <term><option>--nv-index=
</option></term>
453 <listitem><para>Specifies the NV index to store the policy in. Honoured by
454 <command>make-policy
</command>. If not specified the command will automatically pick a free NV
457 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
461 <term><option>--components=
</option></term>
463 <listitem><para>Takes a path to read
<filename>*.pcrlock
</filename> and
464 <filename>*.pcrlock.d/*.pcrlock
</filename> files from. May be used more than once to specify multiple
465 such directories. If not specified defaults to
<filename>/etc/pcrlock.d/
</filename>,
466 <filename>/run/pcrlock.d/
</filename>,
<filename>/var/lib/pcrlock.d/
</filename>,
467 <filename>/usr/local/pcrlock.d/
</filename>,
<filename>/usr/lib/pcrlock.d/
</filename>.
</para>
469 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
473 <term><option>--location=
</option></term>
475 <listitem><para>Takes either a string or a colon-separated pair of strings. Configures up to which
476 point in the sorted list of defined components to analyze/predict PCRs to. Typically, the
477 <command>systemd-pcrlock
</command> tool is invoked from a fully booted system after boot-up and
478 before shutdown. This means various components that are defined for shutdown have not been measured
479 yet, and should not be searched for. This option allows one to restrict which components are
480 considered for analysis (taking only components before some point into account, ignoring components
481 after them). The expected string is ordered against the filenames of the components defined. Any
482 components with a lexicographically later name are ignored. This logic applies to the
483 <command>log
</command>,
<command>predict
</command>, and
<command>make-policy
</command> verbs. If a
484 colon-separated pair of strings are specified then they select which phases of the boot to include
485 in the prediction/policy. The first string defines where the first prediction shall be made, and the
486 second string defines where the last prediction shall be made. All such predictions are then combined
489 <para>If used with
<command>list-components
</command> the selected location range will be highlighted
490 in the component list.
</para>
492 <para>Defaults to
<literal>760-:
940-
</literal>, which means the policies generated by default will
493 basically cover the whole runtime of the OS userspace, from the initrd (as
<literal>760-
</literal>
494 closely follows
<filename>750-enter-initrd.pcrlock
</filename>) until (and including) the main runtime
495 of the system (as
<literal>940-
</literal> is closely followed by
496 <filename>950-shutdown.pcrlock
</filename>). See
497 <citerefentry><refentrytitle>systemd.pcrlock
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
498 for a full list of well-known components, that illustrate where this range is placed by
501 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
505 <term><option>--recovery-pin=
</option></term>
507 <listitem><para>Takes one of
<literal>hide
</literal>,
<literal>show
</literal> or
508 <literal>query
</literal>. Defaults to
<literal>hide
</literal>. Honoured by
509 <command>make-policy
</command>. If
<literal>query
</literal>, will query the user for a PIN to unlock
510 the TPM2 NV index with. If no policy was created before, this PIN is used to protect the newly
511 allocated NV index. If a policy has been created before, the PIN is used to unlock write access to
512 the NV index. If either
<literal>hide
</literal> or
<literal>show
</literal> is used, a PIN is
513 automatically generated, and — only in case of
<literal>show
</literal> — displayed on
514 screen. Regardless if user supplied or automatically generated, it is stored in encrypted form in the
515 policy metadata file. The recovery PIN may be used to regain write access to an NV index in case the
516 access policy became out of date.
</para>
518 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
522 <term><option>--pcrlock=
</option></term>
524 <listitem><para>Takes a file system path as argument. If specified overrides where to write the
525 generated pcrlock data to. Honoured by the various
<command>lock-*
</command> commands. If not
526 specified, a default path is generally used, as documented above.
</para>
528 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
532 <term><option>--policy=
</option></term>
534 <listitem><para>Takes a file system path as argument. If specified overrides where to write pcrlock
535 policy metadata to. If not specified defaults to
536 <filename>/var/lib/systemd/pcrlock.json
</filename>.
</para>
538 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
542 <term><option>--force
</option></term>
544 <listitem><para>If specified with
<command>make-policy
</command>, the predicted policy will be
545 written to the NV index even if it is detected to be the same as the previously stored
548 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
552 <term><option>--entry-token=
</option></term>
554 <listitem><para>Sets the boot entry token to use for the file name for the pcrlock policy credential
555 in the EFI System Partition or XBOOTLDR partition. See the
556 <citerefentry><refentrytitle>bootctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry> option of
557 the same regarding expected values. This switch has an effect on the
558 <command>make-policy
</command> command only.
</para>
560 <xi:include href=
"version-info.xml" xpointer=
"v256"/></listitem>
563 <xi:include href=
"standard-options.xml" xpointer=
"json" />
564 <xi:include href=
"standard-options.xml" xpointer=
"no-pager" />
565 <xi:include href=
"standard-options.xml" xpointer=
"help" />
566 <xi:include href=
"standard-options.xml" xpointer=
"version" />
571 <title>Exit status
</title>
573 <para>On success,
0 is returned, a non-zero failure code otherwise.
</para>
577 <title>See Also
</title>
578 <para><simplelist type=
"inline">
579 <member><citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
580 <member><citerefentry><refentrytitle>systemd.pcrlock
</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
581 <member><citerefentry><refentrytitle>systemd-cryptenroll
</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
582 <member><citerefentry><refentrytitle>systemd-cryptsetup@.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
583 <member><citerefentry><refentrytitle>systemd-repart
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
584 <member><citerefentry><refentrytitle>systemd-pcrmachine.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
585 <member><citerefentry><refentrytitle>systemd-creds
</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
586 <member><citerefentry><refentrytitle>systemd-stub
</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
587 <member><citerefentry><refentrytitle>bootctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>