diff --git a/man/crypttab.xml b/man/crypttab.xml index 3e003156d2..fa60599301 100644 --- a/man/crypttab.xml +++ b/man/crypttab.xml @@ -808,6 +808,22 @@ + + + + Takes an absolute path to a TPM2 pcrlock policy file, as produced by the + systemd-pcrlock1 + tool. This permits locking LUKS2 volumes to a local policy of allowed PCR values with + variants. See + systemd-cryptenroll1 + for details on enrolling TPM2 pcrlock policies. If this option is not specified but it is attempted + to unlock a LUKS2 volume with a TPM2 pcrlock enrollment a suitable signature file + pcrlock.json is searched for in /run/systemd/ and + /var/lib/systemd/ (in this order). + + + + diff --git a/man/rules/meson.build b/man/rules/meson.build index 45a1780fb2..201c9694c6 100644 --- a/man/rules/meson.build +++ b/man/rules/meson.build @@ -1004,6 +1004,16 @@ manpages = [ ['systemd-nspawn', '1', [], ''], ['systemd-oomd.service', '8', ['systemd-oomd'], 'ENABLE_OOMD'], ['systemd-path', '1', [], ''], + ['systemd-pcrlock', + '8', + ['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'], + 'ENABLE_BOOTLOADER'], ['systemd-pcrphase.service', '8', ['systemd-pcrextend', @@ -1138,6 +1148,7 @@ manpages = [ ['systemd.nspawn', '5', [], ''], ['systemd.offline-updates', '7', [], ''], ['systemd.path', '5', [], ''], + ['systemd.pcrlock', '5', ['systemd.pcrlock.d'], ''], ['systemd.preset', '5', [], ''], ['systemd.resource-control', '5', [], ''], ['systemd.scope', '5', [], ''], diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml index 836538be4c..3d0efc9bf7 100644 --- a/man/systemd-cryptenroll.xml +++ b/man/systemd-cryptenroll.xml @@ -519,6 +519,20 @@ + + PATH + + Configures a TPM2 pcrlock policy to bind encryption to. Expects a path to a pcrlock + policy file as generated by the + systemd-pcrlock1 + tool. If a TPM2 device is enrolled and this option is not used but a file + pcrlock.json is found in /run/systemd/ or + /var/lib/systemd/ it is automatically used. Assign an empty string to turn this + behaviour off. + + + + SLOT diff --git a/man/systemd-pcrlock.xml b/man/systemd-pcrlock.xml new file mode 100644 index 0000000000..3c4d9bb0e7 --- /dev/null +++ b/man/systemd-pcrlock.xml @@ -0,0 +1,559 @@ + + + + + + + + systemd-pcrlock + systemd + + + + systemd-pcrlock + 8 + + + + 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 + + + + + /usr/lib/systemd/systemd-pcrlock OPTIONS + + + + + Description + + 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. + + systemd-pcrlock 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. + + systemd-pcrlock uses as input for its analysis and prediction: + + + The UEFI firmware TPM2 event log + (i.e. /sys/kernel/security/tpm0/binary_bios_measurements) of the current + boot. + + The userspace TPM2 event log + (i.e. /run/log/systemd/tpm2-measure.log) of the current + boot. + + The current PCR state of the TPM2 chip. + + Boot component definition files (*.pcrlock and + *.pcrlock.d/*.pcrlock, see + systemd.pcrlock5) + that each define expected measurements for one component of the boot process, permitting alternative + variants for each. (Variants may be used used to bless multiple kernel versions or boot loader versions + at the same time.) + + + 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 PolicyPCR and PolicyOR 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 PolicyAuthorizeNV policy). + + Use tools such as + systemd-cryptenroll1 + or systemd-repart8 to + bind disk encryption to such a systemd-pcrlock TPM2 policy. Specifically, see the + switches of these tools. + + The access policy logic requires a TPM2 device that implements the + PolicyAuthorizeNV command, i.e. implements TPM 2.0 version 1.38 or newer. + + + + Commands + + The following commands are understood: + + + + log + + This reads the combined TPM2 event log, validates it, matches it against the current + PCR values, and outputs both in tabular form. Combine with to generate + output in JSON format. + + + + + + cel + + This reads the combined TPM2 event log and writes it to STDOUT in TCG Common Event Log + Format (CEL-JSON) format. + + + + + + list-components + + Shows a list of component definitions and their variants, i.e. the + *.pcrlock files discovered in /var/lib/pcrlock.d/, + /usr/lib/pcrlock.d/, and the other supported directories. See + systemd.pcrlock5 + for details on these files and the full list of directories searched. + + + + + + predict + + 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. + + + + + + + make-policy + + This predicts the PCR state for future boots, much like the + predict 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 /var/lib/systemd/pcrlock.json. + + The NV index is allocated on first invocation, and updated on subsequent invocations. + + 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 switch. If specified it may be used as + alternative path of access to update the policy. + + If the new prediction matches the old this command terminates quickly and executes no further + operation. (Unless is specified, see below.) + + + + + + + remove-policy + + Removes a previously generated policy. Deletes the + /var/lib/systemd/pcrlock.json file, and deallocates the NV index. + + + + + + + lock-firmware-code + unlock-firmware-code + + Generates/removes .pcrlock files based on the TPM2 event log of + the current boot covering all records for PCRs 0 ("platform-code") and 2 ("external-code"). + + 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. + + 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 unlock-firmware-code before doing a firmware update, + followed by make-policy to refresh the policy. + + systemd-pcrlock lock-firmware-code is invoked automatically at boot via the + systemd-pcrlock-firmware-code.service unit, if enabled. This ensures that an + access policy managed by systemd-pcrlock 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. + + The files are only generated from the event log if the event log matches the current TPM2 PCR + state. + + This writes/removes the files + /var/lib/pcrlock.d/250-firmware-code-early.pcrlock.d/generated.pcrlock and + /var/lib/pcrlock.d/550-firmware-code-late.pcrlock.d/generated.pcrlock. + + + + + + + lock-firmware-config + unlock-firmware-config + + This is similar to + lock-firmware-code/unlock-firmware-code but locks down the + firmware configuration, i.e. PCRs 1 ("platform-config") and 3 ("external-config"). + + 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. + + Use unlock-firmware-config before making firmware configuration changes. If + the systemd-pcrlock-firmware-config.service unit is enabled it will + automatically generate a pcrlock file from the new measurements. + + This writes/removes the files + /var/lib/pcrlock.d/250-firmware-config-early.pcrlock.d/generated.pcrlock and + /var/lib/pcrlock.d/550-firmware-config-late.pcrlock.d/generated.pcrlock. + + + + + + + lock-secureboot-policy + unlock-secureboot-policy + + Generates/removes a .pcrlock 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. + + Use unlock-firmware-config before applying SecureBoot policy updates. If + the systemd-pcrlock-secureboot-policy.service unit is enabled it will + automatically generate a pcrlock file from the policy discovered. + + This writes/removes the file + /var/lib/pcrlock.d/230-secureboot-policy.pcrlock.d/generated.pcrlock. + + + + + + + lock-secureboot-authority + unlock-secureboot-authority + + Generates/removes a .pcrlock 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"). + + This writes/removes the file + /var/lib/pcrlock.d/620-secureboot-authority.pcrlock.d/generated.pcrlock. + + + + + + + lock-gpt DEVICE + unlock-gpt + + Generates/removes a .pcrlock 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"). + + This writes/removes the file + /var/lib/pcrlock.d/600-gpt.pcrlock.d/generated.pcrlock. + + + + + + + lock-pe BINARY + unlock-pe + + Generates/removes a .pcrlock 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 lock-uki (see below) for PE binaries that are unified kernel images + (UKIs). + + Expects a path to the PE binary as argument. If not specified, reads the binary from STDIN + instead. + + The pcrlock file to write must be specified via the switch. + + + + + + + lock-uki UKI + unlock-uki + + Generates/removes a .pcrlock file based on the specified UKI PE + binary. This is useful for predicting measurements the firmware makes to PCR 4 ("boot-loader-code"), + and systemd-stub7 + makes to PCR 11 ("kernel-boot"), if the specified UKI is booted. This is a superset of + lock-pe. + + Expects a path to the UKI PE binary as argument. If not specified, reads the binary from STDIN + instead. + + The pcrlock file to write must be specified via the switch. + + + + + + + lock-machine-id + unlock-machine-id + + Generates/removes a .pcrlock file based on + /etc/machine-id. This is useful for predicting measurements + systemd-pcrmachine.service8 + makes to PCR 15 ("system-identity"). + + This writes/removes the file + /var/lib/pcrlock.d/820-machine-id.pcrlock. + + + + + + + lock-file-system PATH + unlock-file-system PATH + + Generates/removes a .pcrlock file based on file system + identity. This is useful for predicting measurements + systemd-pcrfs@.service8 + makes to PCR 15 ("system-identity") for the root and /var/ file systems. + + This writes/removes the files + /var/lib/pcrlock.d/830-root-file-system.pcrlock and + /var/lib/pcrlock.d/840-file-system-path.pcrlock. + + + + + + + lock-kernel-cmdline FILE + unlock-kernel-cmdline + + Generates/removes a .pcrlock file based on + /proc/cmdline (or the specified file if given). This is useful for predicting + measurements the Linux kernel makes to PCR 9 ("kernel-initrd"). + + This writes/removes the file + /var/lib/pcrlock.d/710-kernel-cmdline.pcrlock/generated.pcrlock. + + + + + + + lock-kernel-initrd FILE + unlock-kernel-initrd + + Generates/removes a .pcrlock 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 systemd-stub UKIs, as the initrd is combined + dynamically from various sources and hence does not take a single input, like this command. + + This writes/removes the file + /var/lib/pcrlock.d/720-kernel-initrd.pcrlock/generated.pcrlock. + + + + + + + lock-raw FILE + unlock-raw + + Generates/removes a .pcrlock 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 + is specified. The generated pcrlock file is written to the file specified + via or to STDOUT (if none is specified). + + + + + + + + + + Options + + The following options are understood: + + + + + + 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. + + + + + + + + Specifies the PCR number to use. May be specified more than once to select multiple + PCRs. + + This is used by lock-raw and lock-pe to select the + PCR to lock against. + + If used with predict and make-policy 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. + + + + + + + + Specifies to NV index to store the policy in. Honoured by + make-policy. If not specified the command will automatically pick a free NV + index. + + + + + + + + Takes a path to read *.pcrlock and + *.pcrlock.d/*.pcrlock files from. May be used more than once to specify multiple + such directories. If not specified defaults to /etc/pcrlock.d/, + /run/pcrlock.d/, /var/lib/pcrlock.d/, + /usr/local/pcrlock.d/, /usr/lib/pcrlock.d/. + + + + + + + + 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 + systemd-pcrlock 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 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 log, + predict, and make-policy 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. + + If used with list-components the selected location range will be highlighted + in the component list. + + Defaults to 760-:940-, which means the policies generated by default will + basically cover the whole runtime of the OS userspace, from the initrd (as 760- + closely follows 750-enter-initrd.pcrlock) until (and including) the main runtime + of the system (as 940- is closely followed by + 950-shutdown.pcrlock). See + systemd.pcrlock5 + for a full list of well-known components, that illustrate where this range is placed by + default. + + + + + + + + Takes a boolean. Defaults to false. Honoured by make-policy. If + true, 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 this option is not used a PIN is automatically + generated. 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. + + + + + + + + Takes a file system path as argument. If specified overrides where to write the + generated pcrlock data to. Honoured by the various lock-* commands. If not + specified, a default path is generally used, as documented above. + + + + + + + + Takes a file system path as argument. If specified overrides where to write pcrlock + policy metadata to. If not specified defaults to + /var/lib/systemd/pcrlock.json. + + + + + + + + If specified with make-policy, the predicted policy will be + written to the NV index even if it is detected to be the same as the previously stored + one. + + + + + + + + + + + + + Exit status + + On success, 0 is returned, a non-zero failure code otherwise. + + + + See Also + + systemd1, + systemd.pcrlock5, + systemd-cryptenroll1, + systemd-cryptsetup@.service8, + systemd-repart8, + systemd-pcrmachine.service8 + + + + diff --git a/man/systemd-repart.xml b/man/systemd-repart.xml index 8517f24d67..70f8346e80 100644 --- a/man/systemd-repart.xml +++ b/man/systemd-repart.xml @@ -388,6 +388,16 @@ + + PATH + + Configures a TPM2 pcrlock policy to bind encryption to. See + systemd-cryptenroll1 + for details on this option. + + + + BOOL diff --git a/man/systemd.pcrlock.xml b/man/systemd.pcrlock.xml new file mode 100644 index 0000000000..070bed2e11 --- /dev/null +++ b/man/systemd.pcrlock.xml @@ -0,0 +1,298 @@ + + + + + + systemd.pcrlock + systemd + + + + systemd.pcrlock + 5 + + + + systemd.pcrlock + systemd.pcrlock.d + PCR measurement prediction files + + + + +/etc/pcrlock.d/*.pcrlock +/etc/pcrlock.d/*.pcrlock.d/*.pcrlock +/run/pcrlock.d/*.pcrlock +/run/pcrlock.d/*.pcrlock.d/*.pcrlock +/var/lib/pcrlock.d/*.pcrlock +/var/lib/pcrlock.d/*.pcrlock.d/*.pcrlock +/usr/local/pcrlock.d/*.pcrlock +/usr/local/pcrlock.d/*.pcrlock.d/*.pcrlock +/usr/lib/pcrlock.d/*.pcrlock +/usr/lib/pcrlock.d/*.pcrlock.d/*.pcrlock + + + + Description + + *.pcrlock files define expected TPM2 PCR measurements of components involved + in the boot + process. systemd-pcrlock1 + uses such pcrlock files to analyze and predict TPM2 PCR measurements. The pcrlock files are JSON arrays + that follow a subset of the TCG Common Event Log Format + (CEL-JSON) specification. Specifically the recnum, content, + and content_type record fields are not used and ignored if present. Each pcrlock file + defines one set of expected, ordered PCR measurements of a specific component of the boot. + + *.pcrlock files may be placed in various .d/ drop-in directores (see above for + a full list). All matching files discovered in these directories are sorted alphabetically by their file + name (without taking the actual directory they were found in into account): pcrlock files with + alphabetically earlier names are expected to cover measurements done before those with alphabetically + later names. In order to make positioning pcrlock files in the boot process convenient the files are + expected (by convention, this is not enforced) to be named + NNN-component.pcrlock (where + NNN is a three-digit decimal number), for example + 750-enter-initrd.pcrlock. + + For various components of the boot process more than one alternative pcrlock file shall be + supported (i.e. "variants"). For example to cover multiple kernels installed in parallel in the access + policy, or multiple versions of the boot loader. This can be done by placing + *.pcrlock.d/*.pcrlock in the drop-in dirs, i.e. a common directory for a specific + component, that contains one or more pcrlock files each covering one variant of the + component. Example: 650-kernel.pcrlock.d/6.5.5-200.fc38.x86_64.pcrlock and + 650-kernel.pcrlock.d/6.5.7-100.fc38.x86_64.pcrlock + + Use systemd-pcrlock list-components to list all pcrlock files currently + installed. + + Use the various lock-* commands of systemd-pcrlock to + automatically generate suitable pcrlock files for various types of resources. + + + + Well-known Components + + Components of the boot process may be defined freely by the administrator or OS vendor. The + following components are well-known however, and are defined by systemd. The list below is useful for + ordering local pcrlock files properly against these components of the boot. + + + + + 240-secureboot-policy.pcrlock + + The SecureBoot policy, as recorded to PCR 7. May be generated via + systemd-pcrlock lock-secureboot-policy. + + + + + + 250-firmware-code-early.pcrlock + + Firmware code measurements, as recorded to PCR 0 and 2, up to the separator + measurement (see 400-secureboot-separator.pcrlock. below). May be generated via + systemd-pcrlock lock-firmware-code. + + + + + + 250-firmware-config-early.pcrlock + + Firmware configuration measurements, as recorded to PCR 1 and 3, up to the separator + measurement (see 400-secureboot-separator.pcrlock. below). May be generated via + systemd-pcrlock lock-firmware-config. + + + + + + 350-action-efi-application.pcrlock + + The EFI "Application" measurement done once by the firmware. Statically defined. + + + + + + 400-secureboot-separator.pcrlock + + The EFI "separator" measurement on PCR 7 done once by the firmware to indicate where + firmware control transitions into boot loader/OS control. Statically defined. + + + + + + 500-separator.pcrlock + + The EFI "separator" measurements on PCRs 0-6 done once by the firmware to indicate + where firmware control transitions into boot loader/OS control. Statically defined. + + + + + + 550-firmware-code-late.pcrlock + + Firmware code measurements, as recorded to PCR 0 and 2, after the separator + measurement (see 400-secureboot-separator.pcrlock. above). May be generated via + systemd-pcrlock lock-firmware-code. + + + + + + 550-firmware-config-late.pcrlock + + Firmware configuration measurements, as recorded to PCR 1 and 3, after the separator + measurement (see 400-secureboot-separator.pcrlock. above). May be generated via + systemd-pcrlock lock-firmware-config. + + + + + + 600-gpt.pcrlock + + The GPT partition table of the booted medium, as recorded to PCR 5 by the + firmware. May be generated via systemd-pcrlock lock-gpt. + + + + + + 620-secureboot-authority.pcrlock + + The SecureBoot authority, as recorded to PCR 7. May be generated via + systemd-pcrlock lock-secureboot-authority. + + + + + + 700-action-efi-exit-boot-services.pcrlock + + The EFI action generated when ExitBootServices() is generated, + i.e. the UEFI environment is left and the OS takes over. Covers the PCR 5 measurement. Statically + defined. + + + + + + 710-kernel-cmdline.pcrlock + + The kernel command line, as measured by the Linux kernel to PCR 9. May be generated + via systemd-pcrlock lock-kernel-cmdline. + + + + + + 720-kernel-initrd.pcrlock + + The kernel initrd, as measured by the Linux kernel to PCR 9. May be generated + via systemd-pcrlock lock-kernel-initrd. + + + + + + 750-enter-initrd.pcrlock + + The measurement to PCR 11 + systemd-pcrphase-initrd.service8 + makes when the initrd initializes. Statically defined. + + + + + + 800-leave-initrd.pcrlock + + The measurement to PCR 11 + systemd-pcrphase-initrd.service8 + makes when the initrd finishes. Statically defined. + + + + + + 820-machine-id.pcrlock + + The measurement to PCR 15 + systemd-pcrmachine.service8 + makes at boot, covering /etc/machine-id contents. May be generated via + systemd-pcrlock lock-machine-id. + + + + + + 830-root-file-system.pcrlock + + The measurement to PCR 15 + systemd-pcrfs-root.service8 + makes at boot, covering the root file system identity. May be generated + via systemd-pcrlock lock-file-system. + + + + + + 850-sysinit.pcrlock + + The measurement to PCR 11 + systemd-pcrphase-sysinit.service8 + makes when the main userspace did basic initialization and will now proceed to start regular system + services. Statically defined. + + + + + + 900-ready.pcrlock + + The measurement to PCR 11 + systemd-pcrphase.service8 + makes when the system fully booted up. Statically defined. + + + + + + 950-shutdown.pcrlock + + The measurement to PCR 11 + systemd-pcrphase.service8 + makes when the system begins shutdown. Statically defined. + + + + + + 990-final.pcrlock + + The measurement to PCR 11 + systemd-pcrphase-sysinit.service8 + makes when the system is close to finishing shutdown. Statically defined. + + + + + + + + See Also + + systemd1, + systemd-pcrlock1 + + + +