Debian Codegraph @

upstream/debian-trixie/man8/systemd-pcrlock.8

raw
1 '\" t
2 .TH "SYSTEMD\-PCRLOCK" "8" "" "systemd 257.13" "systemd-pcrlock"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-pcrlock, systemd-pcrlock-file-system.service, systemd-pcrlock-firmware-code.service, systemd-pcrlock-firmware-config.service, systemd-pcrlock-machine-id.service, systemd-pcrlock-make-policy.service, systemd-pcrlock-secureboot-authority.service, systemd-pcrlock-secureboot-policy.service \- Analyze and predict TPM2 PCR states and generate an access policy from the prediction
24 .SH "SYNOPSIS"
25 .HP \w'\fB/usr/lib/systemd/systemd\-pcrlock\fR\ 'u
26 \fB/usr/lib/systemd/systemd\-pcrlock\fR [OPTIONS...]
27 .SH "DESCRIPTION"
28 .PP
29 Note: this command is experimental for now\&. While it is likely to become a regular component of systemd, it might still change in behaviour and interface\&.
30 .PP
31 \fBsystemd\-pcrlock\fR
32 is a tool that may be used to analyze and predict TPM2 PCR measurements, and generate TPM2 access policies from the prediction which it stores in a TPM2 NV index (i\&.e\&. in the TPM2 non\-volatile memory)\&. This may then be used to restrict access to TPM2 objects (such as disk encryption keys) to system boot\-ups in which only specific, trusted components are used\&.
33 .PP
34 \fBsystemd\-pcrlock\fR
35 uses as input for its analysis and prediction:
36 .sp
37 .RS 4
38 .ie n \{\
39 \h'-04'\(bu\h'+03'\c
40 .\}
41 .el \{\
42 .sp -1
43 .IP \(bu 2.3
44 .\}
45 The UEFI firmware TPM2 event log (i\&.e\&.
46 /sys/kernel/security/tpm0/binary_bios_measurements) of the current boot\&.
47 .RE
48 .sp
49 .RS 4
50 .ie n \{\
51 \h'-04'\(bu\h'+03'\c
52 .\}
53 .el \{\
54 .sp -1
55 .IP \(bu 2.3
56 .\}
57 The userspace TPM2 event log (i\&.e\&.
58 /run/log/systemd/tpm2\-measure\&.log) of the current boot\&.
59 .RE
60 .sp
61 .RS 4
62 .ie n \{\
63 \h'-04'\(bu\h'+03'\c
64 .\}
65 .el \{\
66 .sp -1
67 .IP \(bu 2.3
68 .\}
69 The current PCR state of the TPM2 chip\&.
70 .RE
71 .sp
72 .RS 4
73 .ie n \{\
74 \h'-04'\(bu\h'+03'\c
75 .\}
76 .el \{\
77 .sp -1
78 .IP \(bu 2.3
79 .\}
80 Boot component definition files (*\&.pcrlock
81 and
82 *\&.pcrlock\&.d/*\&.pcrlock, see
83 \fBsystemd.pcrlock\fR(5)) that each define expected measurements for one component of the boot process, permitting alternative variants for each\&. (Variants may be used to bless multiple kernel versions or boot loader versions at the same time\&.)
84 .RE
85 .PP
86 It uses these inputs to generate a combined event log, validating it against the PCR states\&. It then attempts to recognize event log records and matches them against the defined components\&. For each PCR where this can be done comprehensively (i\&.e\&. where all listed records and all defined components have been matched) this may then be used to predict future PCR measurements, taking the alternative variants defined for each component into account\&. This prediction may then be converted into a TPM2 access policy (consisting of TPM2
87 \fBPolicyPCR\fR
88 and
89 \fBPolicyOR\fR
90 items), which is then stored in an NV index in the TPM2\&. This may be used to then lock secrets (such as disk encryption keys) to these policies (via a TPM2
91 \fBPolicyAuthorizeNV\fR
92 policy)\&.
93 .PP
94 Use tools such as
95 \fBsystemd-cryptenroll\fR(1)
96 or
97 \fBsystemd-repart\fR(8)
98 to bind disk encryption to such a
99 \fBsystemd\-pcrlock\fR
100 TPM2 policy\&. Specifically, see the
101 \fB\-\-tpm2\-pcrlock=\fR
102 switches of these tools\&.
103 .PP
104 The access policy logic requires a TPM2 device that implements the
105 "PolicyAuthorizeNV"
106 command, i\&.e\&. implements TPM 2\&.0 version 1\&.38 or newer\&.
107 .SH "COMMANDS"
108 .PP
109 The following commands are understood:
110 .PP
111 \fBlog\fR
112 .RS 4
113 This reads the combined TPM2 event log, validates it, matches it against the current PCR values, and outputs both in tabular form\&. Combine with
114 \fB\-\-json=\fR
115 to generate output in JSON format\&.
116 .sp
117 Added in version 255\&.
118 .RE
119 .PP
120 \fBcel\fR
121 .RS 4
122 This reads the combined TPM2 event log and writes it to STDOUT in
123 \m[blue]\fBTCG Canonical Event Log Format (CEL\-JSON)\fR\m[]\&\s-2\u[1]\d\s+2\&.
124 .sp
125 Added in version 255\&.
126 .RE
127 .PP
128 \fBlist\-components\fR
129 .RS 4
130 Shows a list of component definitions and their variants, i\&.e\&. the
131 *\&.pcrlock
132 files discovered in
133 /var/lib/pcrlock\&.d/,
134 /usr/lib/pcrlock\&.d/, and the other supported directories\&. See
135 \fBsystemd.pcrlock\fR(5)
136 for details on these files and the full list of directories searched\&.
137 .sp
138 Added in version 255\&.
139 .RE
140 .PP
141 \fBpredict\fR
142 .RS 4
143 Predicts the PCR state on future boots\&. This will analyze the TPM2 event log as described above, recognize components, and then generate all possible resulting PCR values for all combinations of component variants\&. Note that no prediction is made for PCRs whose value does not match the event log records, for which unrecognized measurements are discovered or for which components are defined that cannot be found in the event log\&. This is a safety measure to ensure that any generated access policy can be fulfilled correctly on current and future boots\&.
144 .sp
145 Added in version 255\&.
146 .RE
147 .PP
148 \fBmake\-policy\fR
149 .RS 4
150 This predicts the PCR state for future boots, much like the
151 \fBpredict\fR
152 command above\&. It then uses this data to generate a TPM2 access policy which it stores in a TPM2 NV index\&. The prediction and information about the used TPM2 and its NV index are written to
153 /var/lib/systemd/pcrlock\&.json\&.
154 .sp
155 The NV index is allocated on first invocation, and updated on subsequent invocations\&.
156 .sp
157 The NV index contents may be changed (and thus the policy stored in it updated) by providing an access PIN\&. This PIN is normally generated automatically and stored in encrypted form (with an access policy binding it to the NV index itself) in the aforementioned JSON policy file\&. This PIN may be chosen by the user, via the
158 \fB\-\-recovery\-pin=\fR
159 switch\&. If specified it may be used as alternative path of access to update the policy\&.
160 .sp
161 If the new prediction matches the old this command terminates quickly and executes no further operation\&. (Unless
162 \fB\-\-force\fR
163 is specified, see below\&.)
164 .sp
165 Starting with v256, a copy of the
166 /var/lib/systemd/pcrlock\&.json
167 policy file is encoded in a credential (see
168 \fBsystemd-creds\fR(1)
169 for details) and written to the EFI System Partition or XBOOTLDR partition, in the
170 /loader/credentials/
171 subdirectory\&. There it is picked up at boot by
172 \fBsystemd-stub\fR(7)
173 and passed to the invoked initrd, where it can be used to unlock the root file system (which typically contains
174 /var/, which is where the primary copy of the policy is located, which hence cannot be used to unlock the root file system)\&. The credential file is named after the boot entry token of the installation (see
175 \fBbootctl\fR(1)), which is configurable via the
176 \fB\-\-entry\-token=\fR
177 switch, see below\&.
178 .sp
179 Added in version 255\&.
180 .RE
181 .PP
182 \fBremove\-policy\fR
183 .RS 4
184 Removes a previously generated policy\&. Deletes the
185 /var/lib/systemd/pcrlock\&.json
186 file, and deallocates the NV index\&.
187 .sp
188 Added in version 255\&.
189 .RE
190 .PP
191 \fBlock\-firmware\-code\fR, \fBunlock\-firmware\-code\fR
192 .RS 4
193 Generates/removes
194 \&.pcrlock
195 files based on the TPM2 event log of the current boot covering all records for PCRs 0 ("platform\-code") and 2 ("external\-code")\&.
196 .sp
197 This operation allows locking the boot process to the current version of the firmware of the system and its extension cards\&. This operation should only be used if the system vendor does not provide suitable pcrlock data ahead of time\&.
198 .sp
199 Note that this data only matches the current version of the firmware\&. If a firmware update is applied this data will be out\-of\-date and any access policy generated from it will no longer pass\&. It is thus recommended to invoke
200 \fBunlock\-firmware\-code\fR
201 before doing a firmware update, followed by
202 \fBmake\-policy\fR
203 to refresh the policy\&.
204 .sp
205 \fBsystemd\-pcrlock lock\-firmware\-code\fR
206 is invoked automatically at boot via the
207 systemd\-pcrlock\-firmware\-code\&.service
208 unit, if enabled\&. This ensures that an access policy managed by
209 \fBsystemd\-pcrlock\fR
210 is automatically locked to the new firmware version whenever the policy has been relaxed temporarily, in order to cover for firmware updates, as described above\&.
211 .sp
212 The files are only generated from the event log if the event log matches the current TPM2 PCR state\&.
213 .sp
214 This writes/removes the files
215 /var/lib/pcrlock\&.d/250\-firmware\-code\-early\&.pcrlock\&.d/generated\&.pcrlock
216 and
217 /var/lib/pcrlock\&.d/550\-firmware\-code\-late\&.pcrlock\&.d/generated\&.pcrlock\&.
218 .sp
219 Added in version 255\&.
220 .RE
221 .PP
222 \fBlock\-firmware\-config\fR, \fBunlock\-firmware\-config\fR
223 .RS 4
224 This is similar to
225 \fBlock\-firmware\-code\fR/\fBunlock\-firmware\-code\fR
226 but locks down the firmware configuration, i\&.e\&. PCRs 1 ("platform\-config") and 3 ("external\-config")\&.
227 .sp
228 This functionality should be used with care as in most scenarios a minor firmware configuration change should not invalidate access policies to TPM2 objects\&. Also note that some systems measure unstable and unpredictable information (e\&.g\&. current CPU voltages, temperatures, as part of SMBIOS data) to these PCRs, which means this form of lockdown cannot be used reliably on such systems\&. Use this functionality only if the system and hardware is well known and does not suffer by these limitations, for example in virtualized environments\&.
229 .sp
230 Use
231 \fBunlock\-firmware\-config\fR
232 before making firmware configuration changes\&. If the
233 systemd\-pcrlock\-firmware\-config\&.service
234 unit is enabled it will automatically generate a pcrlock file from the new measurements\&.
235 .sp
236 This writes/removes the files
237 /var/lib/pcrlock\&.d/250\-firmware\-config\-early\&.pcrlock\&.d/generated\&.pcrlock
238 and
239 /var/lib/pcrlock\&.d/550\-firmware\-config\-late\&.pcrlock\&.d/generated\&.pcrlock\&.
240 .sp
241 Added in version 255\&.
242 .RE
243 .PP
244 \fBlock\-secureboot\-policy\fR, \fBunlock\-secureboot\-policy\fR
245 .RS 4
246 Generates/removes a
247 \&.pcrlock
248 file based on the SecureBoot policy currently enforced\&. This looks at the SecureBoot, PK, KEK, db, dbx, dbt, dbr EFI variables and predicts their measurements to PCR 7 ("secure\-boot\-policy") on the next boot\&.
249 .sp
250 Use
251 \fBunlock\-firmware\-config\fR
252 before applying SecureBoot policy updates\&. If the
253 systemd\-pcrlock\-secureboot\-policy\&.service
254 unit is enabled it will automatically generate a pcrlock file from the policy discovered\&.
255 .sp
256 This writes/removes the file
257 /var/lib/pcrlock\&.d/230\-secureboot\-policy\&.pcrlock\&.d/generated\&.pcrlock\&.
258 .sp
259 Added in version 255\&.
260 .RE
261 .PP
262 \fBlock\-secureboot\-authority\fR, \fBunlock\-secureboot\-authority\fR
263 .RS 4
264 Generates/removes a
265 \&.pcrlock
266 file based on the SecureBoot authorities used to validate the boot path\&. SecureBoot authorities are the specific SecureBoot database entries that where used to validate the UEFI PE binaries executed at boot\&. This looks at the event log of the current boot, and uses relevant measurements on PCR 7 ("secure\-boot\-policy")\&.
267 .sp
268 This writes/removes the file
269 /var/lib/pcrlock\&.d/620\-secureboot\-authority\&.pcrlock\&.d/generated\&.pcrlock\&.
270 .sp
271 Added in version 255\&.
272 .RE
273 .PP
274 \fBlock\-gpt\fR [\fIDEVICE\fR], \fBunlock\-gpt\fR
275 .RS 4
276 Generates/removes a
277 \&.pcrlock
278 file based on the GPT partition table of the specified disk\&. If no disk is specified automatically determines the block device backing the root file system\&. This locks the state of the disk partitioning of the booted medium, which firmware measures to PCR 5 ("boot\-loader\-config")\&.
279 .sp
280 This writes/removes the file
281 /var/lib/pcrlock\&.d/600\-gpt\&.pcrlock\&.d/generated\&.pcrlock\&.
282 .sp
283 Added in version 255\&.
284 .RE
285 .PP
286 \fBlock\-pe\fR [\fIBINARY\fR], \fBunlock\-pe\fR
287 .RS 4
288 Generates/removes a
289 \&.pcrlock
290 file based on the specified PE binary\&. This is useful for predicting measurements the firmware makes to PCR 4 ("boot\-loader\-code") if the specified binary is part of the UEFI boot process\&. Use this on boot loader binaries and suchlike\&. Use
291 \fBlock\-uki\fR
292 (see below) for PE binaries that are unified kernel images (UKIs)\&.
293 .sp
294 Expects a path to the PE binary as argument\&. If not specified, reads the binary from STDIN instead\&.
295 .sp
296 The pcrlock file to write must be specified via the
297 \fB\-\-pcrlock=\fR
298 switch\&.
299 .sp
300 Added in version 255\&.
301 .RE
302 .PP
303 \fBlock\-uki\fR [\fIUKI\fR], \fBunlock\-uki\fR
304 .RS 4
305 Generates/removes a
306 \&.pcrlock
307 file based on the specified UKI PE binary\&. This is useful for predicting measurements the firmware makes to PCR 4 ("boot\-loader\-code"), and
308 \fBsystemd-stub\fR(7)
309 makes to PCR 11 ("kernel\-boot"), if the specified UKI is booted\&. This is a superset of
310 \fBlock\-pe\fR\&.
311 .sp
312 Expects a path to the UKI PE binary as argument\&. If not specified, reads the binary from STDIN instead\&.
313 .sp
314 The pcrlock file to write must be specified via the
315 \fB\-\-pcrlock=\fR
316 switch\&.
317 .sp
318 Added in version 255\&.
319 .RE
320 .PP
321 \fBlock\-machine\-id\fR, \fBunlock\-machine\-id\fR
322 .RS 4
323 Generates/removes a
324 \&.pcrlock
325 file based on
326 /etc/machine\-id\&. This is useful for predicting measurements
327 \fBsystemd-pcrmachine.service\fR(8)
328 makes to PCR 15 ("system\-identity")\&.
329 .sp
330 This writes/removes the file
331 /var/lib/pcrlock\&.d/820\-machine\-id\&.pcrlock\&.
332 .sp
333 Added in version 255\&.
334 .RE
335 .PP
336 \fBlock\-file\-system\fR [\fIPATH\fR], \fBunlock\-file\-system\fR [\fIPATH\fR]
337 .RS 4
338 Generates/removes a
339 \&.pcrlock
340 file based on file system identity\&. This is useful for predicting measurements
341 \[email protected]\fR(8)
342 makes to PCR 15 ("system\-identity") for the root and
343 /var/
344 file systems\&.
345 .sp
346 This writes/removes the files
347 /var/lib/pcrlock\&.d/830\-root\-file\-system\&.pcrlock
348 and
349 /var/lib/pcrlock\&.d/840\-file\-system\-\fIpath\fR\&.pcrlock\&.
350 .sp
351 Added in version 255\&.
352 .RE
353 .PP
354 \fBlock\-kernel\-cmdline\fR [\fIFILE\fR], \fBunlock\-kernel\-cmdline\fR
355 .RS 4
356 Generates/removes a
357 \&.pcrlock
358 file based on
359 /proc/cmdline
360 (or the specified file if given)\&. This is useful for predicting measurements the Linux kernel makes to PCR 9 ("kernel\-initrd")\&.
361 .sp
362 This writes/removes the file
363 /var/lib/pcrlock\&.d/710\-kernel\-cmdline\&.pcrlock/generated\&.pcrlock\&.
364 .sp
365 Added in version 255\&.
366 .RE
367 .PP
368 \fBlock\-kernel\-initrd\fR \fIFILE\fR, \fBunlock\-kernel\-initrd\fR
369 .RS 4
370 Generates/removes a
371 \&.pcrlock
372 file based on a kernel initrd cpio archive\&. This is useful for predicting measurements the Linux kernel makes to PCR 9 ("kernel\-initrd")\&. Do not use for
373 \fBsystemd-stub\fR(7)
374 UKIs, as the initrd is combined dynamically from various sources and hence does not take a single input, like this command\&.
375 .sp
376 This writes/removes the file
377 /var/lib/pcrlock\&.d/720\-kernel\-initrd\&.pcrlock/generated\&.pcrlock\&.
378 .sp
379 Added in version 255\&.
380 .RE
381 .PP
382 \fBlock\-raw\fR [\fIFILE\fR], \fBunlock\-raw\fR
383 .RS 4
384 Generates/removes a
385 \&.pcrlock
386 file based on raw binary data\&. The data is either read from the specified file or from STDIN (if none is specified)\&. This requires that
387 \fB\-\-pcrs=\fR
388 is specified\&. The generated \&.pcrlock file is written to the file specified via
389 \fB\-\-pcrlock=\fR
390 or to STDOUT (if none is specified)\&.
391 .sp
392 Added in version 255\&.
393 .RE
394 .SH "OPTIONS"
395 .PP
396 The following options are understood:
397 .PP
398 \fB\-\-raw\-description\fR
399 .RS 4
400 When displaying the TPM2 event log do not attempt to decode the records to provide a friendly event log description string\&. Instead, show the binary payload data in escaped form\&.
401 .sp
402 Added in version 255\&.
403 .RE
404 .PP
405 \fB\-\-pcr=\fR
406 .RS 4
407 Specifies the PCR number to use\&. May be specified more than once to select multiple PCRs\&.
408 .sp
409 This is used by
410 \fBlock\-raw\fR
411 and
412 \fBlock\-pe\fR
413 to select the PCR to lock against\&.
414 .sp
415 If used with
416 \fBpredict\fR
417 and
418 \fBmake\-policy\fR
419 this will override which PCRs to include in the prediction and policy\&. If unspecified this defaults to PCRs 0\-5, 7, 11\-15\&. Note that these commands will not include any PCRs in the prediction/policy (even if specified explicitly) if there are measurements in the event log that do not match the current PCR value, or there are unrecognized measurements in the event log, or components define measurements not seen in the event log\&.
420 .sp
421 Added in version 255\&.
422 .RE
423 .PP
424 \fB\-\-nv\-index=\fR
425 .RS 4
426 Specifies the NV index to store the policy in\&. Honoured by
427 \fBmake\-policy\fR\&. If not specified, the command will automatically pick a free NV index\&.
428 .sp
429 Added in version 255\&.
430 .RE
431 .PP
432 \fB\-\-components=\fR
433 .RS 4
434 Takes a path to read
435 *\&.pcrlock
436 and
437 *\&.pcrlock\&.d/*\&.pcrlock
438 files from\&. May be used more than once to specify multiple such directories\&. If not specified, defaults to
439 /etc/pcrlock\&.d/,
440 /run/pcrlock\&.d/,
441 /var/lib/pcrlock\&.d/,
442 /usr/local/lib/pcrlock\&.d/,
443 /usr/lib/pcrlock\&.d/\&.
444 .sp
445 Added in version 255\&.
446 .RE
447 .PP
448 \fB\-\-location=\fR
449 .RS 4
450 Takes either a string or a colon\-separated pair of strings\&. Configures up to which point in the sorted list of defined components to analyze/predict PCRs to\&. Typically, the
451 \fBsystemd\-pcrlock\fR
452 tool is invoked from a fully booted system after boot\-up and before shutdown\&. This means various components that are defined for shutdown have not been measured yet, and should not be searched for\&. This option allows one to restrict which components are considered for analysis (taking only components before some point into account, ignoring components after them)\&. The expected string is ordered against the filenames of the components defined\&. Any components with a lexicographically later name are ignored\&. This logic applies to the
453 \fBlog\fR,
454 \fBpredict\fR, and
455 \fBmake\-policy\fR
456 verbs\&. If a colon\-separated pair of strings are specified then they select which phases of the boot to include in the prediction/policy\&. The first string defines where the first prediction shall be made, and the second string defines where the last prediction shall be made\&. All such predictions are then combined into one set\&.
457 .sp
458 If used with
459 \fBlist\-components\fR
460 the selected location range will be highlighted in the component list\&.
461 .sp
462 Defaults to
463 "760\-:940\-", which means the policies generated by default will basically cover the whole runtime of the OS userspace, from the initrd (as
464 "760\-"
465 closely follows
466 750\-enter\-initrd\&.pcrlock) until (and including) the main runtime of the system (as
467 "940\-"
468 is closely followed by
469 950\-shutdown\&.pcrlock)\&. See
470 \fBsystemd.pcrlock\fR(5)
471 for a full list of well\-known components, that illustrate where this range is placed by default\&.
472 .sp
473 Added in version 255\&.
474 .RE
475 .PP
476 \fB\-\-recovery\-pin=\fR
477 .RS 4
478 Takes one of
479 "hide",
480 "show"
481 or
482 "query"\&. Defaults to
483 "hide"\&. Honoured by
484 \fBmake\-policy\fR\&. If
485 "query", will query the user for a PIN to unlock the TPM2 NV index with\&. If no policy was created before, this PIN is used to protect the newly allocated NV index\&. If a policy has been created before, the PIN is used to unlock write access to the NV index\&. If either
486 "hide"
487 or
488 "show"
489 is used, a PIN is automatically generated, and \(em only in case of
490 "show"
491 \(em displayed on screen\&. Regardless if user supplied or automatically generated, it is stored in encrypted form in the policy metadata file\&. The recovery PIN may be used to regain write access to an NV index in case the access policy became out of date\&.
492 .sp
493 Added in version 255\&.
494 .RE
495 .PP
496 \fB\-\-pcrlock=\fR
497 .RS 4
498 Takes a file system path as argument\&. If specified, configures where to write the generated pcrlock data to\&. Honoured by the various
499 \fBlock\-*\fR
500 commands\&. If not specified, a default path is generally used, as documented above\&.
501 .sp
502 Added in version 255\&.
503 .RE
504 .PP
505 \fB\-\-policy=\fR
506 .RS 4
507 Takes a file system path as argument\&. If specified, configures where to write pcrlock policy metadata to\&. If not specified, defaults to
508 /var/lib/systemd/pcrlock\&.json\&.
509 .sp
510 Added in version 255\&.
511 .RE
512 .PP
513 \fB\-\-force\fR
514 .RS 4
515 If specified with
516 \fBmake\-policy\fR, the predicted policy will be written to the NV index even if it is detected to be the same as the previously stored one\&.
517 .sp
518 Added in version 255\&.
519 .RE
520 .PP
521 \fB\-\-entry\-token=\fR
522 .RS 4
523 Sets the boot entry token to use for the file name for the pcrlock policy credential in the EFI System Partition or XBOOTLDR partition\&. See the
524 \fBbootctl\fR(1)
525 option of the same regarding expected values\&. This switch has an effect on the
526 \fBmake\-policy\fR
527 command only\&.
528 .sp
529 Added in version 256\&.
530 .RE
531 .PP
532 \fB\-\-json=\fR\fB\fIMODE\fR\fR
533 .RS 4
534 Shows output formatted as JSON\&. Expects one of
535 "short"
536 (for the shortest possible output without any redundant whitespace or line breaks),
537 "pretty"
538 (for a pretty version of the same, with indentation and line breaks) or
539 "off"
540 (to turn off JSON output, the default)\&.
541 .RE
542 .PP
543 \fB\-\-no\-pager\fR
544 .RS 4
545 Do not pipe output into a pager\&.
546 .RE
547 .PP
548 \fB\-h\fR, \fB\-\-help\fR
549 .RS 4
550 Print a short help text and exit\&.
551 .RE
552 .PP
553 \fB\-\-version\fR
554 .RS 4
555 Print a short version string and exit\&.
556 .RE
557 .SH "EXIT STATUS"
558 .PP
559 On success, 0 is returned, a non\-zero failure code otherwise\&.
560 .SH "SEE ALSO"
561 .PP
562 \fBsystemd\fR(1), \fBsystemd.pcrlock\fR(5), \fBsystemd-cryptenroll\fR(1), \[email protected]\fR(8), \fBsystemd-repart\fR(8), \fBsystemd-pcrmachine.service\fR(8), \fBsystemd-creds\fR(1), \fBsystemd-stub\fR(7), \fBbootctl\fR(1)
563 .SH "NOTES"
564 .IP " 1." 4
565 TCG Canonical Event Log Format (CEL-JSON)
566 .RS 4
567 \%https://trustedcomputinggroup.org/resource/canonical-event-log-format/
568 .RE