virt-fw-vars-setup(1)

πŸ“¦
version 26.10.2 Β· 3 versions
, in centos-stream 10, fedora 44

✨ NAME ✨

virt-fw-vars-setup β€” the little icon that generates a uefi variable store in json format πŸ’– (it lives in the General Commands Manual section, for the record)


🌸 SYNOPSIS 🌸

virt-fw-vars-setup [--output] [--profile] [--enroll] [--arch]
[--set-pk-cert] [--add-kek-cert] [--add-db-cert] [--set-dbx-update]
[--disable-secure-boot] [-h|--help] [-V|--version]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so bestie, listen. this tool generates a uefi variable store in json format. that's the whole vibe. that's the assignment. periodt. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • --output <FILE> β€” the json variable store output file ✨
    • if you don't specify it, the output goes to stdout instead. no cap.
  • -h, --help β€” prints help (peep the summary with -h) 🫢
  • -V, --version β€” prints version πŸ‘‘

πŸ’œ QUICK SETUP πŸ’œ

  • --profile <NAME> β€” picks the 'db' certificate profile πŸŽ€
    • use uefi* profiles for linux guests, and win* profiles for windows guests. if you're in doubt (and honestly? valid), you can also use the all profile, which includes both and matches the typical configuration of physical hardware. iconic behaviour tbh.
    • Possible values:
      • none: no certificates
      • win11: Windows CA certificates, 2011 + 2023
      • win23: Windows CA certificate, 2023 only
      • win+rom23: Windows CA + Option ROM certificates, 2023 only
      • uefi11: UEFI CA certificates, 2011 + 2023
      • uefi23: UEFI CA certificate, 2023
      • uefi+rom23: UEFI CA + Option ROM certificates, 2023
      • redhat: Red Hat UEFI CA certificate
      • redhat+rom: Red Hat UEFI CA + Option ROM certificates
      • all: Both Windows and UEFI CA certificates, 2011 + 2023
  • --enroll <MODE> [default: redhat] β€” picks the 'PK' enroll mode πŸ”
    • Possible values:
      • mgmt: EFI_CERT_EXTERNAL_MANAGEMENT_GUID
      • redhat: Red Hat Secure Boot (PK/KEK key 1)
      • microsoft: Windows OEM Devices PK
  • --arch <ARCH> β€” picks the efi architecture for the 'dbx' update 🌈
    • by default, the native architecture gets used. she's lowkey effortless like that.
    • Possible values:
      • aa64
      • x64

πŸ“ SPECIFY DETAILS πŸ“

  • --set-pk-cert <FILE> β€” sets the certificate for 'PK' ✨
    • this has higher priority than PK mode. the way she takes precedence? obsessed.
  • --add-kek-cert <FILE> β€” adds a certificate to 'KEK' πŸ’–
    • can be specified multiple times. the default is to enroll the standard microsoft KEK certificates.
  • --add-db-cert <FILE> β€” adds a certificate to 'db' πŸŽ€
    • can be specified multiple times. certificates get enrolled in addition to the profile certificates. use --profile none if you want to specify all certificates explicitly, bestie.
  • --set-dbx-update <FILE> β€” loads the 'dbx' update from a file 🌸
    • if specified, it replaces the compiled-in default update.
  • --disable-secure-boot β€” disables secure boot πŸ™ˆ
    • it enrolls all secure boot variables but disables secure boot. yes, both. that's the whole thing.

πŸ‘‘ VERSION πŸ‘‘

v0.6.6


🧚 AUTHORS 🧚

Gerd Hoffmann <kraxel@redhat.com>


and that's a wrap, my love 🫢 this whole page is virt-fw-vars-setup 0.6.6, straight out of the virt-fw-vars-setup(1) manual. go forth and slay those uefi variables. πŸ’…βœ¨

πŸ“¦ where this page comes from