mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 18:23:32 +08:00
docs: document the new Verity signature partition type, and its UUIDs
This commit is contained in:
Lennart Poettering
parent
c2fa92e7e8
commit
77617993ee
@ -4,7 +4,7 @@ category: Concepts
|
||||
layout: default
|
||||
SPDX-License-Identifier: LGPL-2.1-or-later
|
||||
---
|
||||
# The Discoverable Partitions Specification
|
||||
# The Discoverable Partitions Specification (DPS)
|
||||
|
||||
_TL;DR: Let's automatically discover, mount and enable the root partition,
|
||||
`/home/`, `/srv/`, `/var/` and `/var/tmp/` and the swap partitions based on
|
||||
@ -50,7 +50,7 @@ Interface](https://systemd.io/BOOT_LOADER_INTERFACE).
|
||||
| `77055800-792c-4f94-b39a-98c91b762bb6` | _Root Partition (LoongArch 64-bit)_ | ditto | ditto |
|
||||
| `60d5a7fe-8e7d-435c-b714-3dd8162144e1` | _Root Partition (RISC-V 32-bit)_ | ditto | ditto |
|
||||
| `72ec70a6-cf74-40e6-bd49-4bda08e8f224` | _Root Partition (RISC-V 64-bit)_ | ditto | ditto |
|
||||
| `d13c5d3b-b5d1-422a-b29f-9454fdc89d76` | _Root Verity Partition (x86)_ | A dm-verity superblock followed by hash data | Contains dm-verity integrity hash data for the matching root partition. If this feature is used the partition UUID of the root partition should be the first 128 bits of the root hash of the dm-verity hash data, and the partition UUID of this dm-verity partition should be the final 128 bits of it, so that the root partition and its verity partition can be discovered easily, simply by specifying the root hash. |
|
||||
| `d13c5d3b-b5d1-422a-b29f-9454fdc89d76` | _Root Verity Partition (x86)_ | A dm-verity superblock followed by hash data | Contains dm-verity integrity hash data for the matching root partition. If this feature is used the partition UUID of the root partition should be the first 128 bits of the root hash of the dm-verity hash data, and the partition UUID of this dm-verity partition should be the final 128 bits of it, so that the root partition and its Verity partition can be discovered easily, simply by specifying the root hash. |
|
||||
| `2c7357ed-ebd2-46d9-aec1-23d437ec2bf5` | _Root Verity Partition (x86-64)_ | ditto | ditto |
|
||||
| `7386cdf2-203c-47a9-a498-f2ecce45a2d6` | _Root Verity Partition (32-bit ARM)_ | ditto | ditto |
|
||||
| `df3300ce-d69f-4c92-978c-9bfb0f38d820` | _Root Verity Partition (64-bit ARM/AArch64)_ | ditto | ditto |
|
||||
@ -58,6 +58,14 @@ Interface](https://systemd.io/BOOT_LOADER_INTERFACE).
|
||||
| `f3393b22-e9af-4613-a948-9d3bfbd0c535` | _Root Verity Partition (LoongArch 64-bit)_ | ditto | ditto |
|
||||
| `ae0253be-1167-4007-ac68-43926c14c5de` | _Root Verity Partition (RISC-V 32-bit)_ | ditto | ditto |
|
||||
| `b6ed5582-440b-4209-b8da-5ff7c419ea3d` | _Root Verity Partition (RISC-V 64-bit)_ | ditto | ditto |
|
||||
| `5996fc05-109c-48de-808b-23fa0830b676` | _Root Verity Signature Partition (x86)_ | A serialized JSON object, see below | Contains a root hash and a PKCS#7 signature for it, permitting signed dm-verity GPT images |
|
||||
| `41092b05-9fc8-4523-994f-2def0408b176` | _Root Verity Signature Partition (x86-64)_ | ditto | ditto |
|
||||
| `42b0455f-eb11-491d-98d3-56145ba9d037` | _Root Verity Signature Partition (32-bit ARM)_ | ditto | ditto |
|
||||
| `6db69de6-29f4-4758-a7a5-962190f00ce3` | _Root Verity Signature Partition (64-bit ARM/AArch64)_ | ditto | ditto |
|
||||
| `e98b36ee-32ba-4882-9b12-0ce14655f46a` | _Root Verity Signature Partition (Itanium/IA-64)_ | ditto | ditto |
|
||||
| `5afb67eb-ecc8-4f85-ae8e-ac1e7c50e7d0` | _Root Verity Signature Partition (LoongArch 64-bit)_ | ditto | ditto |
|
||||
| `3a112a75-8729-4380-b4cf-764d79934448` | _Root Verity Signature Partition (RISC-V 32-bit)_ | ditto | ditto |
|
||||
| `efe0f087-ea8d-4469-821a-4c2a96a8386a` | _Root Verity Signature Partition (RISC-V 64-bit)_ | ditto | ditto |
|
||||
| `75250d76-8cc6-458e-bd66-bd47cc81a812` | _`/usr/` Partition (x86)_ | Any native, optionally in LUKS | Similar semantics to root partition, but just the `/usr/` partition. |
|
||||
| `8484680c-9521-48c6-9c11-b0720656f69e` | _`/usr/` Partition (x86-64)_ | ditto | ditto |
|
||||
| `7d0359a3-02b3-4f0a-865c-654403e70625` | _`/usr/` Partition (32-bit ARM)_ | ditto | ditto |
|
||||
@ -74,6 +82,14 @@ Interface](https://systemd.io/BOOT_LOADER_INTERFACE).
|
||||
| `f46b2c26-59ae-48f0-9106-c50ed47f673d` | _`/usr/` Verity Partition (LoongArch 64-bit)_ | ditto | ditto |
|
||||
| `cb1ee4e3-8cd0-4136-a0a4-aa61a32e8730` | _`/usr/` Verity Partition (RISC-V 32-bit)_ | ditto | ditto |
|
||||
| `8f1056be-9b05-47c4-81d6-be53128e5b54` | _`/usr/` Verity Partition (RISC-V 64-bit)_ | ditto | ditto |
|
||||
| `974a71c0-de41-43c3-be5d-5c5ccd1ad2c0` | _`/usr/` Verity Signature Partition (x86)_ | A serialized JSON object, see below | Similar semantics to root Verity signature partition, but just for the `/usr/` partition. |
|
||||
| `e7bb33fb-06cf-4e81-8273-e543b413e2e2` | _`/usr/` Verity Signature Partition (x86-64)_ | ditto | ditto |
|
||||
| `d7ff812f-37d1-4902-a810-d76ba57b975a` | _`/usr/` Verity Signature Partition (32-bit ARM)_ | ditto | ditto |
|
||||
| `c23ce4ff-44bd-4b00-b2d4-b41b3419e02a` | _`/usr/` Verity Signature Partition (64-bit ARM/AArch64)_ | ditto | ditto |
|
||||
| `8de58bc2-2a43-460d-b14e-a76e4a17b47f` | _`/usr/` Verity Signature Partition (Itanium/IA-64)_ | ditto | ditto |
|
||||
| `b024f315-d330-444c-8461-44bbde524e99` | _`/usr/` Verity Signature Partition (LoongArch 64-bit)_ | ditto | ditto |
|
||||
| `c3836a13-3137-45ba-b583-b16c50fe5eb4` | _`/usr/` Verity Signature Partition (RISC-V 32-bit)_ | ditto | ditto |
|
||||
| `d2f9000a-7a18-453f-b5cd-4d32f77a7b32` | _`/usr/` Verity Signature Partition (RISC-V 64-bit)_ | ditto | ditto |
|
||||
| `933ac7e1-2eb4-4f13-b844-0e14e2aef915` | _Home Partition_ | Any native, optionally in LUKS | The first partition with this type UUID on the disk containing the root partition is automatically mounted to `/home/`. If the partition is encrypted with LUKS, the device mapper file will be named `/dev/mapper/home`. |
|
||||
| `3b8f8425-20e0-4f3b-907f-1a25a76f98e8` | _Server Data Partition_ | Any native, optionally in LUKS | The first partition with this type UUID on the disk containing the root partition is automatically mounted to `/srv/`. If the partition is encrypted with LUKS, the device mapper file will be named `/dev/mapper/srv`. |
|
||||
| `4d21b016-b534-45c2-a9fb-5c16e091fd2d` | _Variable Data Partition_ | Any native, optionally in LUKS | The first partition with this type UUID on the disk containing the root partition is automatically mounted to `/var/` — under the condition that its partition UUID matches the first 128 bits of `HMAC-SHA256(machine-id, 0x4d21b016b53445c2a9fb5c16e091fd2d)` (i.e. the SHA256 HMAC hash of the binary type UUID keyed by the machine ID as read from [`/etc/machine-id`](https://www.freedesktop.org/software/systemd/man/machine-id.html). This special requirement is made because `/var/` (unlike the other partition types listed here) is inherently private to a specific installation and cannot possibly be shared between multiple OS installations on the same disk, and thus should be bound to a specific instance of the OS, identified by its machine ID. If the partition is encrypted with LUKS, the device mapper file will be named `/dev/mapper/var`. |
|
||||
@ -87,8 +103,8 @@ Other GPT type IDs might be used on Linux, for example to mark software RAID or
|
||||
LVM partitions. The definitions of those GPT types is outside of the scope of
|
||||
this specification.
|
||||
|
||||
[systemd-id128(1)](http://www.freedesktop.org/software/systemd/man/systemd-id128.html)
|
||||
may be used to list those UUIDs.
|
||||
[systemd-id128(1)](http://www.freedesktop.org/software/systemd/man/systemd-id128.html)'s
|
||||
`show` command may be used to list those GPT partition type UUIDs.
|
||||
|
||||
## Partition Names
|
||||
|
||||
@ -97,31 +113,36 @@ human-friendly, descriptive partition names in the GPT partition table, for
|
||||
example "*Home*", "*Server* *Data*", "*Fedora* *Root*" and similar, possibly
|
||||
localized.
|
||||
|
||||
For the Root/Verity/Verity signature partitions it might make sense to use a
|
||||
versioned naming scheme reflecting the OS name and its version,
|
||||
e.g. "fooOS_2021.4" or similar.
|
||||
|
||||
## Partition Flags
|
||||
|
||||
This specification defines three GPT partition flags that may be set for the
|
||||
partition types defined above:
|
||||
|
||||
1. For the root, `/usr/`, Verity, home, server data, variable data, temporary data,
|
||||
swap and extended boot loader partitions, the partition flag bit 63
|
||||
("*no-auto*") may be used to turn off auto-discovery for the specific
|
||||
partition. If set, the partition will not be automatically mounted or
|
||||
enabled.
|
||||
1. For the root, `/usr/`, Verity, Verity signature, home, server data, variable
|
||||
data, temporary data, swap and extended boot loader partitions, the
|
||||
partition flag bit 63 ("*no-auto*") may be used to turn off auto-discovery
|
||||
for the specific partition. If set, the partition will not be automatically
|
||||
mounted or enabled.
|
||||
|
||||
2. For the root, `/usr/`, Verity, home, server data, variable data, temporary
|
||||
data and extended boot loader partitions, the partition flag bit 60
|
||||
("*read-only*") may be used to mark a partition for read-only mounts only.
|
||||
If set, the partition will be mounted read-only instead of read-write. Note
|
||||
that the variable data partition and the temporary data partition will
|
||||
generally not be able to serve their purpose if marked read-only, since by
|
||||
their very definition they are supposed to be mutable. (The home and server
|
||||
data partitions are generally assumed to be mutable as well, but the
|
||||
requirement for them is not equally strong.) Because of that, while the
|
||||
read-only flag is defined and supported, it's almost never a good idea to
|
||||
actually use it for these partitions. Also note that Verity partitions are
|
||||
by their semantics always read-only. The flag is hence of little effect for
|
||||
them, and it is recommended to set it unconditionally for the Verity
|
||||
partition types.
|
||||
2. For the root, `/usr/`, Verity, Verity signature home, server data, variable
|
||||
data, temporary data and extended boot loader partitions, the partition flag
|
||||
bit 60 ("*read-only*") may be used to mark a partition for read-only mounts
|
||||
only. If set, the partition will be mounted read-only instead of
|
||||
read-write. Note that the variable data partition and the temporary data
|
||||
partition will generally not be able to serve their purpose if marked
|
||||
read-only, since by their very definition they are supposed to be
|
||||
mutable. (The home and server data partitions are generally assumed to be
|
||||
mutable as well, but the requirement for them is not equally strong.)
|
||||
Because of that, while the read-only flag is defined and supported, it's
|
||||
almost never a good idea to actually use it for these partitions. Also note
|
||||
that Verity and signature partitions are by their semantics always
|
||||
read-only. The flag is hence of little effect for them, and it is
|
||||
recommended to set it unconditionally for the Verity and signature partition
|
||||
types.
|
||||
|
||||
3. For the root, `/usr/`, home, server data, variable data, temporary data and
|
||||
extended boot loader partitions, the partition flag bit 59
|
||||
@ -129,11 +150,11 @@ partition types defined above:
|
||||
of the contained file system to the size of the partition when
|
||||
mounted. Tools that automatically mount disk image with a GPT partition
|
||||
table are suggested to implicitly grow the contained file system to the
|
||||
partition size they are contained in. This flag is without effect on
|
||||
partitions marked read-only.
|
||||
partition size they are contained in, if they are found to be smaller. This
|
||||
flag is without effect on partitions marked read-only.
|
||||
|
||||
Note that the first two flag definitions happen to map nicely to the ones used
|
||||
by Microsoft Basic Data Partitions.
|
||||
Note that the first two flag definitions happen to correspond nicely to the
|
||||
same ones used by Microsoft Basic Data Partitions.
|
||||
|
||||
All three of these flags generally affect only auto-discovery and automatic
|
||||
mounting of disk images. If partitions marked with these flags are mounted
|
||||
@ -142,6 +163,63 @@ using low-level commands like
|
||||
[mount(2)](https://man7.org/linux/man-pages/man2/mount.2.html), they typically
|
||||
have no effect.
|
||||
|
||||
## Verity
|
||||
|
||||
The Root/`/usr/` partition types and their matching Verity and Verity signature
|
||||
partitions enable relatively automatic handling of `dm-verity` protected
|
||||
setups. These types are defined with two modes of operation in mind:
|
||||
|
||||
1. A trusted Verity root hash is passed in externally, for example is specified
|
||||
on the kernel command line that is signed along with the kernel image using
|
||||
SecureBoot PE signing (which in turn is tested against a set of
|
||||
firmware-provided set of signing keys). If so, discovery and setup of a
|
||||
Verity volume may be fully automatic: if the root partition's UUID is chosen
|
||||
to match the first 128 bit of the root hash, and the matching Verity
|
||||
partition UUIDs is chosen to match the last 128bit of the root hash, then
|
||||
automatic discovery and match-up of the two partitions is possible, as the
|
||||
root hash is enough to both find the partitions and then combine them in a
|
||||
Verity volume. In this mode a Verity signature partition is not used and
|
||||
unnecessary.
|
||||
|
||||
2. A Verity signature partition is included on the disk, with a signature to be
|
||||
tested against a system-provided set of signing keys. The signature
|
||||
partition primarily contains two fields: the root hash to use, and a PKCS#7
|
||||
signature of it, using a signature key trusted by the OS. If so, discovery
|
||||
and setup of a Verity volume may be fully automatic. First, the specified
|
||||
root hash is validated with the signature and the OS-provided trusted
|
||||
keys. If the signature checks out the root hash is then used in the same way
|
||||
as in the first mode of operation described above.
|
||||
|
||||
Both modes of operation may be combined in a single image. This is particularly
|
||||
useful for images that shall be usable in two different contexts: for example
|
||||
an image that shall be able to boot directly on UEFI systems (in which
|
||||
case it makes sense to include the root hash on the kernel command line that is
|
||||
included in the signed kernel image to boot, as per mode of operation #1
|
||||
above), but also be able to used as image for a container engine (such as
|
||||
`systemd-nspawn`), which can use the signature partition to validate the image,
|
||||
without making use of the signed kernel image (and thus following mode of
|
||||
operation #2).
|
||||
|
||||
The Verity signature partition's contents should be a serialized JSON object in
|
||||
text form, padded with NUL bytes to the next multiple of 4096 bytes in
|
||||
size. Currently three fields are defined for the JSON object:
|
||||
|
||||
1. The (mandatory) `rootHash` field should be a string containing the Verity root hash,
|
||||
formatted as series of (lowercase) hex characters.
|
||||
|
||||
2. The (mandatory) `signature` field should be a string containing the PKCS#7
|
||||
signature of the root hash, in Base64-encoded DER format. This should be the
|
||||
same format used by the Linux kernel's dm-verity signature logic, i.e. the
|
||||
signed data should be the exact string representation of the hash, as stored
|
||||
in `rootHash` above.
|
||||
|
||||
3. The (optional) `certificateFingerprint` field should be a string containing
|
||||
a SHA256 fingerprint of the X.509 certificate for the key that signed the
|
||||
root hash, formatted as series of (lowercase) hex characters (no `:`
|
||||
separators or such).
|
||||
|
||||
More fields might be added in later revisions of this specification.
|
||||
|
||||
## Suggested Mode of Operation
|
||||
|
||||
An *installer* that repartitions the hard disk _should_ use the above UUID
|
||||
@ -158,20 +236,20 @@ An *installer* _may_ omit creating entries in `/etc/fstab` for root, `/home/`,
|
||||
`/srv/`, `/var/`, `/var/tmp` and for the swap partitions if they use these UUID
|
||||
partition types, and are the first partitions on the disk of each type. If the
|
||||
ESP shall be mounted to `/efi/` (or `/boot/`), it may additionally omit
|
||||
creating the entry for it in `/etc/fstab`. If an extended boot partition is
|
||||
used, or if the EFI partition shall not be mounted to `/efi/` or `/boot/`, it
|
||||
_must_ create `/etc/fstab` entries for them. If other partitions are used (for
|
||||
example for `/usr/` or `/var/lib/mysql/`), the installer _must_ register these
|
||||
in `/etc/fstab`. The `root=` parameter passed to the kernel by the boot loader
|
||||
may be omitted if the root partition is the first one on the disk of its type.
|
||||
If the root partition is not the first one on the disk, the `root=` parameter
|
||||
_must_ be passed to the kernel by the boot loader. An installer that mounts a
|
||||
root, `/usr/`, `/home/`, `/srv/`, `/var/`, or `/var/tmp/` file system with the
|
||||
partition types defined as above which contains a LUKS header _must_ call the
|
||||
device mapper device "root", "usr", "home", "srv", "var" or "tmp",
|
||||
respectively. This is necessary to ensure that the automatic discovery will
|
||||
never result in different device mapper names than any static configuration by
|
||||
the installer, thus eliminating possible naming conflicts and ambiguities.
|
||||
creating the entry for it in `/etc/fstab`. If the EFI partition shall not be
|
||||
mounted to `/efi/` or `/boot/`, it _must_ create `/etc/fstab` entries for them.
|
||||
If other partitions are used (for example for `/usr/local/` or
|
||||
`/var/lib/mysql/`), the installer _must_ register these in `/etc/fstab`. The
|
||||
`root=` parameter passed to the kernel by the boot loader may be omitted if the
|
||||
root partition is the first one on the disk of its type. If the root partition
|
||||
is not the first one on the disk, the `root=` parameter _must_ be passed to the
|
||||
kernel by the boot loader. An installer that mounts a root, `/usr/`, `/home/`,
|
||||
`/srv/`, `/var/`, or `/var/tmp/` file system with the partition types defined
|
||||
as above which contains a LUKS header _must_ call the device mapper device
|
||||
"root", "usr", "home", "srv", "var" or "tmp", respectively. This is necessary
|
||||
to ensure that the automatic discovery will never result in different device
|
||||
mapper names than any static configuration by the installer, thus eliminating
|
||||
possible naming conflicts and ambiguities.
|
||||
|
||||
An *operating* *system* _should_ automatically discover and mount the first
|
||||
root partition that does not have the no-auto flag set (as described above) by
|
||||
|
||||
Loading…
Reference in New Issue
Block a user