Debian Codegraph @

upstream/debian-unstable/man1/ukify.1

raw
1 '\" t
2 .TH "UKIFY" "1" "" "systemd 261~rc3" "ukify"
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 ukify \- Combine components into a signed Unified Kernel Image for UEFI systems
24 .SH "SYNOPSIS"
25 .HP \w'\fBukify\fR\ 'u
26 \fBukify\fR [OPTIONS...] build
27 .HP \w'\fBukify\fR\ 'u
28 \fBukify\fR [OPTIONS...] genkey
29 .HP \w'\fBukify\fR\ 'u
30 \fBukify\fR [OPTIONS...] inspect FILE...
31 .SH "DESCRIPTION"
32 .PP
33 \fBukify\fR
34 is a tool whose primary purpose is to combine components (usually a kernel, an initrd, and the
35 \fBsystemd-stub\fR(7)
36 UEFI stub) to create a
37 \m[blue]\fBUAPI\&.5 Unified Kernel Image (UKI)\fR\m[]\&\s-2\u[1]\d\s+2
38 \(em a single PE binary that boots the system\&. When the UKI is executed, the stub extracts and boots the embedded linux kernel\&. The UKI can be started directly by the firmware or through a boot loader\&. When used with
39 \m[blue]\fBqemu\fR\m[]\&\s-2\u[2]\d\s+2, a UKI can also be executed through "direct kernel boot", see example below\&.
40 .PP
41 \fBukify\fR
42 can also be used generate other types of UKI\-like images, in particular extensions\&. See the description of the
43 \fBbuild\fR
44 verb below\&.
45 \fBukify\fR
46 can also generate certificates and keys for SecureBoot and PCR signing, see the description of the
47 \fBgenkey\fR
48 verb below\&.
49 \fBukify\fR
50 can also print detailed information about unified kernel images, see the description of
51 \fBinspect\fR
52 verb below\&.
53 .SH "COMMANDS"
54 .PP
55 The following commands are understood:
56 .SS "build"
57 .PP
58 This command creates a Unified Kernel Image\&. The two primary options that should be specified for the
59 \fBbuild\fR
60 verb are
61 \fILinux=\fR/\fB\-\-linux=\fR, and
62 \fIInitrd=\fR/\fB\-\-initrd=\fR\&.
63 \fIInitrd=\fR
64 accepts multiple whitespace\-separated paths and
65 \fB\-\-initrd=\fR
66 can be specified multiple times\&.
67 .PP
68 Additional sections will be inserted into the UKI, either automatically or only if a specific option is provided\&. See the discussions of
69 \fIMicrocode=\fR/\fB\-\-microcode=\fR,
70 \fICmdline=\fR/\fB\-\-cmdline=\fR,
71 \fIOSRelease=\fR/\fB\-\-os\-release=\fR,
72 \fIDeviceTree=\fR/\fB\-\-devicetree=\fR,
73 \fIDeviceTreeAuto=\fR/\fB\-\-devicetree\-auto=\fR,
74 \fIHWIDs=\fR/\fB\-\-hwids=\fR,
75 \fISplash=\fR/\fB\-\-splash=\fR,
76 \fIPCRPKey=\fR/\fB\-\-pcrpkey=\fR,
77 \fIUname=\fR/\fB\-\-uname=\fR,
78 \fISBAT=\fR/\fB\-\-sbat=\fR, and
79 \fB\-\-section=\fR
80 below\&.
81 .PP
82 \fBukify\fR
83 can also be used to assemble a PE binary that is not executable but contains auxiliary data, for example additional kernel command line entries\&.
84 .PP
85 If PCR signing keys are provided via the
86 \fIPCRPrivateKey=\fR/\fB\-\-pcr\-private\-key=\fR
87 and
88 \fIPCRPublicKey=\fR/\fB\-\-pcr\-public\-key=\fR
89 or
90 \fIPCRCertificate=\fR/\fB\-\-pcr\-certificate=\fR
91 options, PCR values that will be seen after booting with the given kernel, initrd, and other sections, will be calculated, signed, and embedded in the UKI\&.
92 \fBsystemd-measure\fR(1)
93 is used to perform this calculation and signing\&.
94 .PP
95 The calculation of PCR values is done for specific boot phase paths\&. Those can be specified with the
96 \fIPhases=\fR/\fB\-\-phases=\fR
97 option\&. If not specified, the default provided by
98 \fBsystemd\-measure\fR
99 is used\&. It is also possible to specify the
100 \fIPCRPrivateKey=\fR/\fB\-\-pcr\-private\-key=\fR,
101 \fIPCRPublicKey=\fR/\fB\-\-pcr\-public\-key=\fR
102 or
103 \fIPCRCertificate=\fR/\fB\-\-pcr\-certificate=\fR, and
104 \fIPhases=\fR/\fB\-\-phases=\fR
105 arguments more than once\&. Signatures will then be performed with each of the specified keys\&. On the command line, when both
106 \fB\-\-phases=\fR
107 and
108 \fB\-\-pcr\-private\-key=\fR
109 are used, they must be specified the same number of times, and then the n\-th boot phase path set will be signed by the n\-th key\&. This can be used to build different trust policies for different phases of the boot\&. In the config file,
110 \fIPCRPrivateKey=\fR,
111 \fIPCRPublicKey=\fR, and
112 \fIPhases=\fR
113 are grouped into separate sections, describing separate boot phases\&. If one of
114 \fISigningEngine=\fR/\fB\-\-signing\-engine=\fR
115 or
116 \fISigningProvider=\fR/\fB\-\-signing\-provider=\fR
117 is specified, then the private key arguments will be passed verbatim to
118 \fBopenssl\fR(1)
119 as URIs, and the public key arguments will be loaded as X\&.509 certificates, so that signing can be performed with an OpenSSL engine or provider respectively\&.
120 .PP
121 If a SecureBoot signing key is provided via the
122 \fISecureBootPrivateKey=\fR/\fB\-\-secureboot\-private\-key=\fR
123 option, the resulting PE binary will be signed as a whole, allowing the resulting UKI to be trusted by SecureBoot\&. Also see the discussion of automatic enrollment in
124 \fBsystemd-boot\fR(7)\&.
125 .PP
126 If the stub and/or the kernel contain
127 "\&.sbat"
128 sections they will be merged in the UKI so that revocation updates affecting either are considered when the UKI is loaded by Shim\&. For more information on SBAT see
129 \m[blue]\fBShim documentation\fR\m[]\&\s-2\u[3]\d\s+2\&.
130 .SS "genkey"
131 .PP
132 This command creates the keys for PCR signing and the key and certificate used for SecureBoot signing\&. The same configuration options that determine what keys and in which paths will be needed for signing when
133 \fBbuild\fR
134 is used, here determine which keys will be created\&. See the discussion of
135 \fIPCRPrivateKey=\fR/\fB\-\-pcr\-private\-key=\fR,
136 \fIPCRPublicKey=\fR/\fB\-\-pcr\-public\-key=\fR, and
137 \fISecureBootPrivateKey=\fR/\fB\-\-secureboot\-private\-key=\fR
138 below\&.
139 .PP
140 The output files must not exist\&.
141 .SS "inspect"
142 .PP
143 Display information about the sections in a given binary or binaries\&. If
144 \fB\-\-all\fR
145 is given, all sections are shown\&. Otherwise, if
146 \fB\-\-section=\fR
147 option is specified at least once, only those sections are shown\&. Otherwise, well\-known sections that are typically included in an UKI are shown\&. For each section, its name, size, and sha256\-digest is printed\&. For text sections, the contents are printed\&.
148 .PP
149 Also see the description of
150 \fB\-j\fR/\fB\-\-json=\fR
151 and
152 \fB\-\-section=\fR\&.
153 .PP
154 Other tools that may be useful for inspect UKIs:
155 \fBllvm-objdump\fR(1)
156 \fB\-p\fR
157 and
158 \fBpe\-inspect\fR\&.
159 .SH "CONFIGURATION SETTINGS"
160 .PP
161 Settings can appear in configuration files (the syntax with
162 \fISomeSetting=\fR\fI\fIvalue\fR\fR) and on the command line (the syntax with
163 \fB\-\-some\-setting=\fR\fB\fIvalue\fR\fR)\&. For some command line parameters, a single\-letter shortcut is also allowed\&. In the configuration files, the setting must be in the appropriate section, so the descriptions are grouped by section below\&. When the same setting appears in the configuration file and on the command line, generally the command line setting has higher priority and overwrites the config file setting completely\&. If some setting behaves differently, this is described below\&.
164 .PP
165 If no config file is provided via the option
166 \fB\-\-config=\fR\fB\fIPATH\fR\fR,
167 \fBukify\fR
168 will try to look for a default configuration file in the following paths in this order:
169 /etc/systemd/ukify\&.conf,
170 /run/systemd/ukify\&.conf,
171 /usr/local/lib/systemd/ukify\&.conf, and
172 /usr/lib/systemd/ukify\&.conf, and then load the first one found\&.
173 \fBukify\fR
174 will proceed normally if no configuration file is specified and no default one is found\&.
175 .PP
176 The
177 \fILINUX\fR
178 and
179 \fIINITRD\fR
180 positional arguments, or the equivalent
181 \fILinux=\fR
182 and
183 \fIInitrd=\fR
184 settings, are optional\&. If more than one initrd is specified, they will all be combined into a single PE section\&. This is useful to, for example, prepend microcode before the actual initrd\&.
185 .PP
186 The following options and settings are understood:
187 .SS "Command line\-only options"
188 .PP
189 \fB\-\-config=\fR\fB\fIPATH\fR\fR
190 .RS 4
191 Load configuration from the given config file\&. In general, settings specified in the config file have lower precedence than the settings specified via options\&. In cases where the command line option does not fully override the config file setting are explicitly mentioned in the descriptions of individual options\&.
192 .sp
193 Added in version 254\&.
194 .RE
195 .PP
196 \fB\-\-measure\fR, \fB\-\-no\-measure\fR
197 .RS 4
198 Enable or disable a call to
199 \fBsystemd-measure\fR(1)
200 to print pre\-calculated PCR values\&. Defaults to false\&.
201 .sp
202 Added in version 253\&.
203 .RE
204 .PP
205 \fB\-\-policy\-digest\fR, \fB\-\-no\-policy\-digest\fR
206 .RS 4
207 Enable or disable a call to
208 \fBsystemd-measure\fR(1)
209 to print pre\-calculated TPM2 policy digests\&. Useful for offline signing of PCR policies\&. Defaults to false\&.
210 .sp
211 Added in version 258\&.
212 .RE
213 .PP
214 \fB\-\-section=\fR\fB\fINAME\fR\fR\fB:\fR\fB\fITEXT\fR\fR\fB|\fR\fB\fI@PATH\fR\fR, \fB\-\-section=\fR\fB\fINAME\fR\fR\fB:text|binary\fR\fB[@\fIPATH\fR]\fR
215 .RS 4
216 For all verbs except
217 \fBinspect\fR, the first syntax is used\&. Specify an arbitrary additional section
218 "\fINAME\fR"\&. The argument may be a literal string, or
219 "@"
220 followed by a path name\&. This option may be specified more than once\&. Any sections specified in this fashion will be inserted (in order) before the
221 "\&.linux"
222 section which is always last\&.
223 .sp
224 For the
225 \fBinspect\fR
226 verb, the second syntax is used\&. The section
227 \fINAME\fR
228 will be inspected (if found)\&. If the second argument is
229 "text", the contents will be printed\&. If the third argument is given, the contents will be saved to the file named
230 \fIPATH\fR\&.
231 .sp
232 Note that the name is used as\-is, and if the section name should start with a dot, it must be included in
233 \fINAME\fR\&.
234 .sp
235 Added in version 253\&.
236 .RE
237 .PP
238 \fB\-\-join\-profile=\fR\fB\fIPATH\fR\fR
239 .RS 4
240 Takes a path to an existing PE file containing an additional profile to add to the unified kernel image\&. The profile can be generated beforehand with
241 \fBukify\fR\&. The profile does not need to be signed or contain PCR measurements\&. All UKI PE sections of the specified PE file are copied into the generated UKI\&. This is useful for generating multi\-profile UKIs\&. Note that this only copies PE sections that are defined by the UKI specification, and ignores any other, for example
242 "\&.text"
243 or similar\&.
244 .sp
245 Added in version 257\&.
246 .RE
247 .PP
248 \fB\-\-sign\-profile=\fR\fB\fIID\fR\fR
249 .RS 4
250 Takes a profile ID for which signed PCR measurements should be generated by ukify\&. This option can be used together with
251 \fB\-\-join\-profile=\fR
252 when building the final unified kernel image\&. If not specified, signed PCR measurements will be added for all profiles\&.
253 .sp
254 Added in version 258\&.
255 .RE
256 .PP
257 \fB\-\-join\-pcrsig=\fR\fB\fIPATH\fR\fR, \fB\-\-pcrsig=\fR\fB\fITEXT\fR\fR\fB|\fR\fB\fI@PATH\fR\fR
258 .RS 4
259 \fB\-\-join\-pcrsig=\fR
260 takes a path to an existing PE file containing a previously built UKI\&.
261 \fB\-\-pcrsig=\fR
262 takes a path to an existing pcrsig JSON blob, or a verbatim inline blob\&. They must be used together, and without specifying any other UKI section parameters\&.
263 \fBukify\fR
264 will attach the pcrsig JSON blob to the UKI\&. This is useful in combination with
265 \fB\-\-policy\-digest\fR
266 to create a UKI and then sign the TPM2 policy digests offline\&.
267 .sp
268 Added in version 258\&.
269 .RE
270 .PP
271 \fB\-\-tools=\fR\fB\fIDIRS\fR\fR
272 .RS 4
273 Specify one or more directories with helper tools\&.
274 \fBukify\fR
275 will look for helper tools in those directories first, and if not found, try to load them from
276 \fI$PATH\fR
277 in the usual fashion\&.
278 .sp
279 Added in version 253\&.
280 .RE
281 .PP
282 \fB\-\-output=\fR\fB\fIFILENAME\fR\fR
283 .RS 4
284 The output filename\&. If not specified, the name of the
285 \fILINUX\fR
286 argument, with the suffix
287 "\&.unsigned\&.efi"
288 or
289 "\&.signed\&.efi"
290 will be used, depending on whether signing for SecureBoot was performed\&.
291 .sp
292 Added in version 253\&.
293 .RE
294 .PP
295 \fB\-\-summary\fR
296 .RS 4
297 Print a summary of loaded config and exit\&. This is useful to check how the options from the configuration file and the command line are combined\&.
298 .sp
299 Added in version 254\&.
300 .RE
301 .PP
302 \fB\-\-all\fR
303 .RS 4
304 Print all sections (with
305 \fBinspect\fR
306 verb)\&.
307 .sp
308 Added in version 255\&.
309 .RE
310 .PP
311 \fB\-\-json\fR
312 .RS 4
313 Generate JSON output (with
314 \fBinspect\fR
315 verb)\&.
316 .sp
317 Added in version 255\&.
318 .RE
319 .PP
320 \fB\-h\fR, \fB\-\-help\fR
321 .RS 4
322 Print a short help text and exit\&.
323 .RE
324 .PP
325 \fB\-\-version\fR
326 .RS 4
327 Print a short version string and exit\&.
328 .RE
329 .SS "[UKI] section"
330 .PP
331 \fILinux=\fR\fI\fILINUX\fR\fR, \fB\-\-linux=\fR\fB\fILINUX\fR\fR
332 .RS 4
333 A path to the kernel binary\&.
334 .sp
335 Added in version 254\&.
336 .RE
337 .PP
338 \fIOSRelease=\fR\fI\fITEXT\fR\fR\fI|\fR\fI\fI@PATH\fR\fR, \fB\-\-os\-release=\fR\fB\fITEXT\fR\fR\fB|\fR\fB\fI@PATH\fR\fR
339 .RS 4
340 The os\-release description (the
341 "\&.osrel"
342 section)\&. The argument may be a literal string, or
343 "@"
344 followed by a path name\&. If not specified, the
345 \fBos-release\fR(5)
346 file will be picked up from the host system\&. If explicitly set to an empty string, the "\&.osrel" section is omitted from the UKI (this is not recommended in most cases, and causes the resulting artifact to not be recognized as a UKI by other tools like
347 \fBkernel\-install\fR
348 and
349 \fBbootctl\fR)\&.
350 .sp
351 Added in version 253\&.
352 .RE
353 .PP
354 \fICmdline=\fR\fI\fITEXT\fR\fR\fI|\fR\fI\fI@PATH\fR\fR, \fB\-\-cmdline=\fR\fB\fITEXT\fR\fR\fB|\fR\fB\fI@PATH\fR\fR
355 .RS 4
356 The kernel command line (the
357 "\&.cmdline"
358 section)\&. The argument may be a literal string, or
359 "@"
360 followed by a path name\&. If not specified, no command line will be embedded\&.
361 .sp
362 Added in version 253\&.
363 .RE
364 .PP
365 \fIInitrd=\fR\fI\fIINITRD\fR\fR\fI\&.\&.\&.\fR, \fB\-\-initrd=\fR\fB\fILINUX\fR\fR
366 .RS 4
367 Zero or more initrd paths\&. In the configuration file, items are separated by whitespace\&. The initrds are combined in the order of specification, with the initrds specified in the config file first\&.
368 .sp
369 Added in version 254\&.
370 .RE
371 .PP
372 \fIMicrocode=\fR\fI\fIUCODE\fR\fR, \fB\-\-microcode=\fR\fB\fIUCODE\fR\fR
373 .RS 4
374 Path to initrd containing microcode updates\&. If not specified, the section will not be present\&.
375 .sp
376 Added in version 256\&.
377 .RE
378 .PP
379 \fISplash=\fR\fI\fIPATH\fR\fR, \fB\-\-splash=\fR\fB\fIPATH\fR\fR
380 .RS 4
381 A picture to display during boot (the
382 "\&.splash"
383 section)\&. The argument is a path to a BMP file\&. If not specified, the section will not be present\&.
384 .sp
385 Added in version 253\&.
386 .RE
387 .PP
388 \fIDeviceTree=\fR\fI\fIPATH\fR\fR, \fB\-\-devicetree=\fR\fB\fIPATH\fR\fR
389 .RS 4
390 The devicetree description (the
391 "\&.dtb"
392 section)\&. The argument is a path to a compiled binary DeviceTree file\&. If not specified, the section will not be present\&.
393 .sp
394 Added in version 253\&.
395 .RE
396 .PP
397 \fIDeviceTreeAuto=\fR\fI\fIPATH\fR\fR\fI\&.\&.\&.\fR, \fB\-\-devicetree\-auto=\fR\fB\fIPATH\fR\fR
398 .RS 4
399 Zero or more automatically selectable DeviceTree files\&. In the configuration file, items are separated by whitespace\&. Each DeviceTree will be in a separate
400 "\&.dtbauto"
401 section\&.
402 .sp
403 Added in version 257\&.
404 .RE
405 .PP
406 \fIHWIDs=\fR\fI\fIPATH\fR\fR, \fB\-\-hwids=\fR\fB\fIPATH\fR\fR
407 .RS 4
408 The hardware ID device table (the
409 "\&.hwids"
410 section)\&. The argument is a path to a directory with JSON HWID device description files\&. Each file needs to contain a single JSON object with a
411 "name",
412 "compatible"
413 and
414 "hwids"
415 keys\&. The
416 "name"
417 and
418 "compatible"
419 keys must have string values and the
420 "hwids"
421 key must have a list of strings as value, where the strings must be valid UUIDs that represent CHIDs/HWIDs\&. Example:
422 .sp
423 .if n \{\
424 .RS 4
425 .\}
426 .nf
427 {
428 "type": "devicetree",
429 "name": "Example Laptop 16 Gen 7",
430 "compatible": "example,laptop\-16\-g7",
431 "hwids": [
432 "5dc05bf4\-01f6\-4089\-b464\-a08c47ea9295",
433 "3e3f8f3c\-2003\-46f2\-811c\-85554f7d5952"
434 ]
435 }
436 .fi
437 .if n \{\
438 .RE
439 .\}
440 .sp
441 Here
442 "Example Laptop 16 Gen 7"
443 is the device
444 "name"
445 (as defined by the manufacturer),
446 "example,laptop\-16\-g7"
447 is the
448 "compatible"
449 (as defined by the kernel) and
450 "hwids"
451 is an array of CHIDs/HWIDs (extracted i\&.e\&. from
452 \fBfwupdtool hwids\fR
453 output)\&. If not specified, and the
454 "/usr/lib/systemd/boot/hwids/[EFI_ARCH]/"
455 directory exists, then the section will be automatically populated from that directory (specify an empty string as the parameter for this option to disable this behavior), otherwise it will not be present\&. It is recommended to specify this parameter if automatically selectable DeviceTrees are to be used\&.
456 .sp
457 Added in version 257\&.
458 .RE
459 .PP
460 \fIUname=\fR\fI\fIVERSION\fR\fR, \fB\-\-uname=\fR\fB\fIVERSION\fR\fR
461 .RS 4
462 Specify the kernel version (as in
463 \fBuname \-r\fR, the
464 "\&.uname"
465 section)\&. If not specified, an attempt will be made to extract the version string from the kernel image\&. It is recommended to pass this explicitly if known, because the extraction is based on heuristics and not very reliable\&. If not specified and extraction fails, the section will not be present\&.
466 .sp
467 Added in version 253\&.
468 .RE
469 .PP
470 \fISBAT=\fR\fI\fITEXT\fR\fR\fI|\fR\fI\fI@PATH\fR\fR, \fB\-\-sbat=\fR\fB\fITEXT\fR\fR\fB|\fR\fB\fI@PATH\fR\fR
471 .RS 4
472 SBAT metadata associated with the UKI or addon\&. SBAT policies are useful to revoke whole groups of UKIs or addons with a single, static policy update that does not take space in DBX/MOKX\&. If not specified manually, a default metadata entry consisting of
473 .sp
474 .if n \{\
475 .RS 4
476 .\}
477 .nf
478 uki,1,UKI,uki,1,https://uapi\-group\&.org/specifications/specs/unified_kernel_image/
479 .fi
480 .if n \{\
481 .RE
482 .\}
483 .sp
484 for UKIs and
485 .sp
486 .if n \{\
487 .RS 4
488 .\}
489 .nf
490 uki\-addon,1,UKI Addon,addon,1,https://www\&.freedesktop\&.org/software/systemd/man/latest/systemd\-stub\&.html
491 .fi
492 .if n \{\
493 .RE
494 .\}
495 .sp
496 for addons will be used, to ensure it is always possible to revoke them\&. For more information on SBAT see
497 \m[blue]\fBShim documentation\fR\m[]\&\s-2\u[3]\d\s+2\&.
498 .sp
499 Added in version 254\&.
500 .RE
501 .PP
502 \fIPCRPKey=\fR\fI\fIPATH\fR\fR, \fB\-\-pcrpkey=\fR\fB\fIPATH\fR\fR
503 .RS 4
504 A path to a public key to embed in the
505 "\&.pcrpkey"
506 section\&. If not specified, and there\*(Aqs exactly one
507 \fIPCRPublicKey=\fR/\fB\-\-pcr\-public\-key=\fR
508 or
509 \fIPCRCertificate=\fR/\fB\-\-pcr\-certificate=\fR
510 argument, that key will be used\&. Otherwise, the section will not be present\&.
511 .sp
512 Added in version 253\&.
513 .RE
514 .PP
515 \fIProfile=\fR\fI\fIPATH\fR\fR, \fB\-\-profile=\fR\fB\fIPATH\fR\fR
516 .RS 4
517 A path to a UKI profile to place in an
518 "\&.profile"
519 section\&. This option is useful for creating multi\-profile UKIs, and is typically used in combination with
520 \fB\-\-join\-profile=\fR, to extend the specified UKI with an additional profile\&.
521 .sp
522 Added in version 257\&.
523 .RE
524 .PP
525 \fIPCRBanks=\fR\fI\fIPATH\fR\fR, \fB\-\-pcr\-banks=\fR\fB\fIPATH\fR\fR
526 .RS 4
527 A comma or space\-separated list of PCR banks to sign a policy for\&. If not present, all known banks will be used ("sha1",
528 "sha256",
529 "sha384",
530 "sha512"), which will fail if not supported by the system\&.
531 .sp
532 Added in version 253\&.
533 .RE
534 .PP
535 \fISecureBootSigningTool=\fR\fI\fISIGNER\fR\fR, \fB\-\-signtool=\fR\fB\fISIGNER\fR\fR
536 .RS 4
537 Whether to use
538 "sbsign",
539 "pesign", or
540 "systemd\-sbsign"\&. Depending on this choice, different parameters are required in order to sign an image\&. Defaults to
541 "sbsign"\&.
542 .sp
543 Added in version 254\&.
544 .RE
545 .PP
546 \fISecureBootPrivateKey=\fR\fI\fISB_KEY\fR\fR, \fB\-\-secureboot\-private\-key=\fR\fB\fISB_KEY\fR\fR
547 .RS 4
548 A path to a private key to use for signing of the resulting binary\&. If the
549 \fISigningEngine=\fR/\fB\-\-signing\-engine=\fR
550 or
551 \fISigningProvider=\fR/\fB\-\-signing\-provider=\fR
552 option is used, this may also be an engine or provider specific designation\&. This option is required by
553 \fISecureBootSigningTool=sbsign\fR/\fB\-\-signtool=sbsign\fR
554 and
555 \fISecureBootSigningTool=systemd\-sbsign\fR/\fB\-\-signtool=systemd\-sbsign\fR\&.
556 .sp
557 Added in version 253\&.
558 .RE
559 .PP
560 \fISecureBootCertificate=\fR\fI\fISB_CERT\fR\fR, \fB\-\-secureboot\-certificate=\fR\fB\fISB_CERT\fR\fR
561 .RS 4
562 A path to a certificate to use for signing of the resulting binary\&. If the
563 \fISigningEngine=\fR/\fB\-\-signing\-engine=\fR
564 or
565 \fISigningProvider=\fR/\fB\-\-signing\-provider=\fR
566 option is used, this may also be an engine or provider specific designation\&. This option is required by
567 \fISecureBootSigningTool=sbsign\fR/\fB\-\-signtool=sbsign\fR
568 and
569 \fISecureBootSigningTool=systemd\-sbsign\fR/\fB\-\-signtool=systemd\-sbsign\fR\&.
570 .sp
571 Added in version 253\&.
572 .RE
573 .PP
574 \fISecureBootCertificateDir=\fR\fI\fISB_PATH\fR\fR, \fB\-\-secureboot\-certificate\-dir=\fR\fB\fISB_PATH\fR\fR
575 .RS 4
576 A path to a nss certificate database directory to use for signing of the resulting binary\&. Takes effect when
577 \fISecureBootSigningTool=pesign\fR/\fB\-\-signtool=pesign\fR
578 is used\&. Defaults to
579 /etc/pki/pesign\&.
580 .sp
581 Added in version 254\&.
582 .RE
583 .PP
584 \fISecureBootCertificateName=\fR\fI\fISB_CERTNAME\fR\fR, \fB\-\-secureboot\-certificate\-name=\fR\fB\fISB_CERTNAME\fR\fR
585 .RS 4
586 The name of the nss certificate database entry to use for signing of the resulting binary\&. This option is required by
587 \fISecureBootSigningTool=pesign\fR/\fB\-\-signtool=pesign\fR\&.
588 .sp
589 Added in version 254\&.
590 .RE
591 .PP
592 \fISecureBootCertificateValidity=\fR\fI\fIDAYS\fR\fR, \fB\-\-secureboot\-certificate\-validity=\fR\fB\fIDAYS\fR\fR
593 .RS 4
594 Period of validity (in days) for a certificate created by
595 \fBgenkey\fR\&. Defaults to 3650, i\&.e\&. 10 years\&.
596 .sp
597 Added in version 254\&.
598 .RE
599 .PP
600 \fISigningEngine=\fR\fI\fIENGINE\fR\fR, \fB\-\-signing\-engine=\fR\fB\fIENGINE\fR\fR
601 .RS 4
602 An OpenSSL engine to be used for signing the resulting binary and PCR measurements, see
603 \fBopenssl-engine\fR(1)\&.
604 .sp
605 Added in version 253\&.
606 .RE
607 .PP
608 \fISigningProvider=\fR\fI\fIPROVIDER\fR\fR, \fB\-\-signing\-provider=\fR\fB\fIPROVIDER\fR\fR
609 .RS 4
610 An OpenSSL provider to be used for signing the resulting binary and PCR measurements, see
611 \fBprovider\fR(7)\&. This option can only be used when
612 \fBsystemd\-sbsign\fR
613 is used as the signing tool\&.
614 .sp
615 Added in version 257\&.
616 .RE
617 .PP
618 \fICertificateProvider=\fR\fI\fIPROVIDER\fR\fR, \fB\-\-certificate\-provider=\fR\fB\fIPROVIDER\fR\fR
619 .RS 4
620 An OpenSSL provider to be used for loading the certificate used to sign the resulting binary and PCR measurements, see
621 \fBprovider\fR(7)\&. This option can only be used when
622 \fBsystemd\-sbsign\fR
623 is used as the signing tool\&.
624 .sp
625 Added in version 257\&.
626 .RE
627 .PP
628 \fISignKernel=\fR\fI\fIBOOL\fR\fR, \fB\-\-sign\-kernel\fR, \fB\-\-no\-sign\-kernel\fR
629 .RS 4
630 Override the detection of whether to sign the Linux binary itself before it is embedded in the combined image\&. If not specified, it will be signed if a SecureBoot signing key is provided via the
631 \fISecureBootPrivateKey=\fR/\fB\-\-secureboot\-private\-key=\fR
632 option and the binary has not already been signed\&. If
633 \fISignKernel=\fR/\fB\-\-sign\-kernel\fR
634 is true, and the binary has already been signed, the signature will be appended anyway\&.
635 .sp
636 Added in version 253\&.
637 .RE
638 .SS "[PCRSignature:\fINAME\fR] section"
639 .PP
640 In the config file, those options are grouped by section\&. On the command line, they must be specified in the same order\&. The sections specified in both sources are combined\&.
641 .PP
642 \fIPCRPrivateKey=\fR\fI\fIPATH\fR\fR, \fB\-\-pcr\-private\-key=\fR\fB\fIPATH\fR\fR
643 .RS 4
644 A private key to use for signing PCR policies\&. On the command line, this option may be specified more than once, in which case multiple signatures will be made\&.
645 .sp
646 Added in version 253\&.
647 .RE
648 .PP
649 \fIPCRPublicKey=\fR\fI\fIPATH\fR\fR, \fB\-\-pcr\-public\-key=\fR\fB\fIPATH\fR\fR
650 .RS 4
651 A public key to use for signing PCR policies\&.
652 .sp
653 On the command line, this option may be specified more than once, similarly to the
654 \fB\-\-pcr\-private\-key=\fR
655 option\&. If not present, the public keys will be extracted from the private keys\&. On the command line, if present, this option must be specified the same number of times as the
656 \fB\-\-pcr\-private\-key=\fR
657 option\&. Cannot be specified if
658 \fB\-\-pcr\-certificate=\fR
659 is used\&.
660 .sp
661 Added in version 253\&.
662 .RE
663 .PP
664 \fIPCRCertificate=\fR\fI\fIPATH\fR\fR, \fB\-\-pcr\-certificate=\fR\fB\fIPATH\fR\fR
665 .RS 4
666 An X\&.509 certificate to use for signing PCR policies\&.
667 .sp
668 On the command line, this option may be specified more than once, similarly to the
669 \fB\-\-pcr\-private\-key=\fR
670 option\&. If not present, the public keys will be extracted from the private keys\&. On the command line, if present, this option must be specified the same number of times as the
671 \fB\-\-pcr\-private\-key=\fR
672 option\&. Cannot be specified if
673 \fB\-\-pcr\-public\-key=\fR
674 is used\&.
675 .sp
676 Added in version 258\&.
677 .RE
678 .PP
679 \fIPhases=\fR\fI\fILIST\fR\fR, \fB\-\-phases=\fR\fB\fILIST\fR\fR
680 .RS 4
681 A comma or space\-separated list of colon\-separated phase paths to sign a policy for\&. Each set of boot phase paths will be signed with the corresponding private key\&. If not present, the default of
682 \fBsystemd-measure\fR(1)
683 will be used\&.
684 .sp
685 On the command line, when this argument is present, it must appear the same number of times as the
686 \fB\-\-pcr\-private\-key=\fR
687 option\&.
688 .sp
689 Added in version 253\&.
690 .RE
691 .SH "EXAMPLES"
692 .PP
693 \fBExample\ \&1.\ \&Minimal invocation\fR
694 .sp
695 .if n \{\
696 .RS 4
697 .\}
698 .nf
699 $ ukify build \e
700 \-\-linux=/lib/modules/6\&.0\&.9\-300\&.fc37\&.x86_64/vmlinuz \e
701 \-\-initrd=/some/path/initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img \e
702 \-\-cmdline=\*(Aqquiet rw\*(Aq
703 .fi
704 .if n \{\
705 .RE
706 .\}
707 .PP
708 This creates an unsigned UKI
709 \&./vmlinuz\&.unsigned\&.efi\&.
710 .PP
711 \fBExample\ \&2.\ \&Direct kernel boot in a virtual machine\fR
712 .PP
713 When using
714 \m[blue]\fBqemu\fR\m[]\&\s-2\u[2]\d\s+2
715 with
716 \m[blue]\fBOVMF\fR\m[]\&\s-2\u[4]\d\s+2
717 (UEFI Firmware for virtual machines) the
718 \fB\-kernel\fR
719 switch can be used directly with a UKI\&. Example:
720 .PP
721 \fBqemu\-kvm \-drive if=pflash,format=qcow2,readonly=on,file=/usr/share/edk2/ovmf/OVMF_CODE_4M\&.qcow2 \-kernel \fR\fB\&./vmlinuz\&.unsigned\&.efi\fR\fB \fR\fB\fI[ \&.\&.\&. ]\fR\fR\fB \fR
722 .PP
723 (The path to the firmware file might need to be adjusted depending on the distribution\&.) Usually, another
724 \fB\-drive\fR
725 argument would to be used to attach an actual disk image, but this is not required\&.
726 .PP
727 \fBExample\ \&3.\ \&All the bells and whistles\fR
728 .sp
729 .if n \{\
730 .RS 4
731 .\}
732 .nf
733 $ ukify build \e
734 \-\-linux=/lib/modules/6\&.0\&.9\-300\&.fc37\&.x86_64/vmlinuz \e
735 \-\-initrd=early_cpio \e
736 \-\-initrd=/some/path/initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img \e
737 \-\-sbat=\*(Aqsbat,1,SBAT Version,sbat,1,https://github\&.com/rhboot/shim/blob/main/SBAT\&.md
738 uki\&.author\&.myimage,1,UKI for System,uki\&.author\&.myimage,1,https://uapi\-group\&.org/specifications/specs/unified_kernel_image/\*(Aq \e
739 \-\-pcr\-private\-key=tpm2\-pcr\-initrd\-private\-key\&.pem \e
740 \-\-pcr\-public\-key=tpm2\-pcr\-initrd\-public\-key\&.pem \e
741 \-\-phases=\*(Aqenter\-initrd\*(Aq \e
742 \-\-pcr\-private\-key=tpm2\-pcr\-private\-key\-system\&.pem \e
743 \-\-pcr\-public\-key=tpm2\-pcr\-public\-key\-system\&.pem \e
744 \-\-phases=\*(Aqenter\-initrd:leave\-initrd enter\-initrd:leave\-initrd:sysinit \e
745 enter\-initrd:leave\-initrd:sysinit:ready\*(Aq \e
746 \-\-pcr\-banks=sha384,sha512 \e
747 \-\-secureboot\-private\-key=secureboot\-private\-key\&.pem \e
748 \-\-secureboot\-certificate=secureboot\-certificate\&.pem \e
749 \-\-sign\-kernel \e
750 \-\-cmdline=\*(Aqquiet rw rhgb\*(Aq
751 .fi
752 .if n \{\
753 .RE
754 .\}
755 .PP
756 This creates a signed UKI
757 \&./vmlinuz\&.signed\&.efi\&. The initrd section contains two concatenated parts,
758 early_cpio
759 and
760 initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img\&. The policy embedded in the
761 "\&.pcrsig"
762 section will be signed for the initrd (the
763 \fBenter\-initrd\fR
764 phase) with the key
765 tpm2\-pcr\-initrd\-private\-key\&.pem, and for the main system (phases
766 \fBleave\-initrd\fR,
767 \fBsysinit\fR,
768 \fBready\fR) with the key
769 tpm2\-pcr\-private\-key\-system\&.pem\&. The Linux binary and the resulting combined image will be signed with the SecureBoot key
770 secureboot\-private\-key\&.pem\&.
771 .PP
772 \fBExample\ \&4.\ \&All the bells and whistles, via a config file\fR
773 .PP
774 This is the same as the previous example, but this time the configuration is stored in a file:
775 .sp
776 .if n \{\
777 .RS 4
778 .\}
779 .nf
780 $ cat ukify\&.conf
781 [UKI]
782 Initrd=early_cpio
783 Cmdline=quiet rw rhgb
784
785 SecureBootPrivateKey=secureboot\-private\-key\&.pem
786 SecureBootCertificate=secureboot\-certificate\&.pem
787 SignKernel=yes
788 PCRBanks=sha384,sha512
789
790 [PCRSignature:initrd]
791 PCRPrivateKey=tpm2\-pcr\-initrd\-private\-key\&.pem
792 PCRPublicKey=tpm2\-pcr\-initrd\-public\-key\&.pem
793 Phases=enter\-initrd
794
795 [PCRSignature:system]
796 PCRPrivateKey=tpm2\-pcr\-private\-key\-system\&.pem
797 PCRPublicKey=tpm2\-pcr\-public\-key\-system\&.pem
798 Phases=enter\-initrd:leave\-initrd
799 enter\-initrd:leave\-initrd:sysinit
800 enter\-initrd:leave\-initrd:sysinit:ready
801
802 $ ukify \-c ukify\&.conf build \e
803 \-\-linux=/lib/modules/6\&.0\&.9\-300\&.fc37\&.x86_64/vmlinuz \e
804 \-\-initrd=/some/path/initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img
805 .fi
806 .if n \{\
807 .RE
808 .\}
809 .PP
810 One "initrd" (early_cpio) is specified in the config file, and the other initrd (initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img) is specified on the command line\&. This may be useful for example when the first initrd contains microcode for the CPU and does not need to be updated when the kernel version changes, unlike the actual initrd\&.
811 .PP
812 \fBExample\ \&5.\ \&Kernel command line PE addon\fR
813 .sp
814 .if n \{\
815 .RS 4
816 .\}
817 .nf
818 ukify build \e
819 \-\-secureboot\-private\-key=secureboot\-private\-key\&.pem \e
820 \-\-secureboot\-certificate=secureboot\-certificate\&.pem \e
821 \-\-cmdline=\*(Aqdebug\*(Aq \e
822 \-\-sbat=\*(Aqsbat,1,SBAT Version,sbat,1,https://github\&.com/rhboot/shim/blob/main/SBAT\&.md
823 uki\-addon\&.author,1,UKI Addon for System,uki\-addon\&.author,1,https://www\&.freedesktop\&.org/software/systemd/man/systemd\-stub\&.html\*(Aq
824 \-\-output=debug\&.addon\&.efi
825 .fi
826 .if n \{\
827 .RE
828 .\}
829 .PP
830 This creates a signed PE binary that contains the additional kernel command line parameter
831 "debug"
832 with SBAT metadata referring to the owner of the addon\&.
833 .PP
834 \fBExample\ \&6.\ \&Decide signing policy, and create certificate and keys\fR
835 .PP
836 First, let\*(Aqs create a configuration file that specifies what signatures shall be made:
837 .sp
838 .if n \{\
839 .RS 4
840 .\}
841 .nf
842 # cat >/etc/kernel/uki\&.conf <<EOF
843 [UKI]
844 SecureBootPrivateKey=/etc/kernel/secureboot\-private\-key\&.pem
845 SecureBootCertificate=/etc/kernel/secureboot\-certificate\&.pem
846
847 [PCRSignature:initrd]
848 Phases=enter\-initrd
849 PCRPrivateKey=/etc/systemd/tpm2\-pcr\-initrd\-private\-key\&.pem
850 PCRPublicKey=/etc/systemd/tpm2\-pcr\-initrd\-public\-key\&.pem
851
852 [PCRSignature:system]
853 Phases=enter\-initrd:leave\-initrd enter\-initrd:leave\-initrd:sysinit
854 enter\-initrd:leave\-initrd:sysinit:ready
855 PCRPrivateKey=/etc/systemd/tpm2\-pcr\-private\-key\-system\&.pem
856 PCRPublicKey=/etc/systemd/tpm2\-pcr\-public\-key\-system\&.pem
857 EOF
858 .fi
859 .if n \{\
860 .RE
861 .\}
862 .PP
863 Next, we can generate the certificate and keys:
864 .sp
865 .if n \{\
866 .RS 4
867 .\}
868 .nf
869 # ukify genkey \-\-config=/etc/kernel/uki\&.conf
870 Writing SecureBoot private key to /etc/kernel/secureboot\-private\-key\&.pem
871 Writing SecureBoot certificate to /etc/kernel/secureboot\-certificate\&.pem
872 Writing private key for PCR signing to /etc/systemd/tpm2\-pcr\-initrd\-private\-key\&.pem
873 Writing public key for PCR signing to /etc/systemd/tpm2\-pcr\-initrd\-public\-key\&.pem
874 Writing private key for PCR signing to /etc/systemd/tpm2\-pcr\-private\-key\-system\&.pem
875 Writing public key for PCR signing to /etc/systemd/tpm2\-pcr\-public\-key\-system\&.pem
876 .fi
877 .if n \{\
878 .RE
879 .\}
880 .PP
881 (Both operations need to be done as root to allow write access to
882 /etc/kernel/\&.)
883 .PP
884 Subsequent invocations using the config file (\fBukify build \-\-config=/etc/kernel/uki\&.conf\fR) will use this certificate and key files\&. Note that the
885 \fBkernel-install\fR(8)
886 plugin
887 60\-ukify\&.install
888 uses
889 /etc/kernel/uki\&.conf
890 by default, so after this file has been created, installations of kernels that create a UKI on the local machine using
891 \fBkernel\-install\fR
892 will perform signing using this config\&.
893 .PP
894 \fBExample\ \&7.\ \&Multi\-Profile UKI\fR
895 .PP
896 First, create a few profiles:
897 .sp
898 .if n \{\
899 .RS 4
900 .\}
901 .nf
902 $ ukify build \e
903 \-\-profile=\*(AqTITLE=Base\*(Aq \e
904 \-\-output=profile0\&.efi
905 .fi
906 .if n \{\
907 .RE
908 .\}
909 .PP
910 Add a second profile (@1):
911 .sp
912 .if n \{\
913 .RS 4
914 .\}
915 .nf
916 $ ukify build \e
917 \-\-profile=\*(AqTITLE=Boot into Storage Target Mode
918 ID=storagetm\*(Aq \e
919 \-\-cmdline=\*(Aqquiet rw rd\&.systemd\&.unit=storage\-target\-mode\&.target\*(Aq \e
920 \-\-output=profile1\&.efi
921 .fi
922 .if n \{\
923 .RE
924 .\}
925 .PP
926 Add a third profile (@2):
927 .sp
928 .if n \{\
929 .RS 4
930 .\}
931 .nf
932 $ ukify build \e
933 \-\-profile=\*(AqTITLE=Factory Reset
934 ID=factory\-reset\*(Aq \e
935 \-\-cmdline=\*(Aqquiet rw systemd\&.unit=factory\-reset\&.target\*(Aq \e
936 \-\-output=profile2\&.efi
937 .fi
938 .if n \{\
939 .RE
940 .\}
941 .PP
942 Then, create a UKI and include all the generated profiles:
943 .sp
944 .if n \{\
945 .RS 4
946 .\}
947 .nf
948 $ ukify build \e
949 \-\-linux=/lib/modules/6\&.0\&.9\-300\&.fc37\&.x86_64/vmlinuz \e
950 \-\-initrd=/some/path/initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img \e
951 \-\-cmdline=\*(Aqquiet rw\*(Aq \e
952 \-\-join\-profile=profile0\&.efi \e
953 \-\-join\-profile=profile1\&.efi \e
954 \-\-join\-profile=profile2\&.efi \e
955 \-\-output=base\&.efi
956 .fi
957 .if n \{\
958 .RE
959 .\}
960 .PP
961 The resulting UKI
962 base\-with\-profile\-0\-1\-2\&.efi
963 will now contain three profiles\&.
964 .PP
965 \fBExample\ \&8.\ \&Offline signing of pcrsig section\fR
966 .PP
967 First, create a UKI and save the PCR JSON blob:
968 .sp
969 .if n \{\
970 .RS 4
971 .\}
972 .nf
973 $ ukify build \e
974 \-\-linux=/lib/modules/6\&.0\&.9\-300\&.fc37\&.x86_64/vmlinuz \e
975 \-\-initrd=/some/path/initramfs\-6\&.0\&.9\-300\&.fc37\&.x86_64\&.img \e
976 \-\-cmdline=\*(Aqquiet rw\*(Aq \e
977 \-\-pcr\-public\-key=tpm2\-pcr\-initrd\-public\-key\&.pem \e
978 \-\-policy\-digest \e
979 \-\-json=short \e
980 \-\-output=base\&.efi >base\&.pcrs
981 .fi
982 .if n \{\
983 .RE
984 .\}
985 .PP
986 Then, sign the PCR digests offline and insert them in the JSON blob:
987 .sp
988 .if n \{\
989 .RS 4
990 .\}
991 .nf
992 #!/usr/bin/python3
993 import base64, json, subprocess
994
995 priv_key = \*(Aq/home/zbyszek/src/systemd/tpm2\-pcr\-private\&.pem\*(Aq
996 base_file = \*(Aqbase\&.pcrs\*(Aq
997
998 base = json\&.load(open(base_file))
999
1000 for bank,policies in base\&.items():
1001 for policy in policies:
1002 pol = base64\&.b16decode(policy[\*(Aqpol\*(Aq]\&.upper())
1003 call = subprocess\&.run([\*(Aqopenssl\*(Aq, \*(Aqdgst\*(Aq, f\*(Aq\-{bank}\*(Aq, \*(Aq\-sign\*(Aq, priv_key],
1004 input=pol,
1005 check=True,
1006 capture_output=True)
1007 sig = base64\&.b64encode(call\&.stdout)\&.decode()
1008 policy[\*(Aqsig\*(Aq] = sig
1009
1010 print(json\&.dumps(base))
1011 .fi
1012 .if n \{\
1013 .RE
1014 .\}
1015 .PP
1016 Finally, attach the updated JSON blob to the UKI:
1017 .sp
1018 .if n \{\
1019 .RS 4
1020 .\}
1021 .nf
1022 $ ukify build \e
1023 \-\-join\-pcrsig=base\&.efi \e
1024 \-\-pcrsig=@base\&.pcrs \e
1025 \-\-json=short \e
1026 \-\-output=base\-signed\&.efi
1027 .fi
1028 .if n \{\
1029 .RE
1030 .\}
1031 .PP
1032 The resulting UKI
1033 base\-signed\&.efi
1034 will now contain the signed PCR digests\&.
1035 .SH "SEE ALSO"
1036 .PP
1037 \fBsystemd\fR(1), \fBsystemd-stub\fR(7), \fBsystemd-boot\fR(7), \fBsystemd-measure\fR(1), \fBsystemd-pcrphase.service\fR(8)
1038 .SH "NOTES"
1039 .IP " 1." 4
1040 UAPI.5 Unified Kernel Image (UKI)
1041 .RS 4
1042 \%https://uapi-group.org/specifications/specs/unified_kernel_image/
1043 .RE
1044 .IP " 2." 4
1045 qemu
1046 .RS 4
1047 \%https://www.qemu.org/docs/master/
1048 .RE
1049 .IP " 3." 4
1050 Shim documentation
1051 .RS 4
1052 \%https://github.com/rhboot/shim/blob/main/SBAT.md
1053 .RE
1054 .IP " 4." 4
1055 OVMF
1056 .RS 4
1057 \%https://www.linux-kvm.org/downloads/lersek/ovmf-whitepaper-c770f8c.txt
1058 .RE