CERT-TO-EFI-HASH-LIST(1)
π cert-to-efi-hash-list β like, the whole manual but make it make sense π
okay so bestie, welcome to cert-to-efi-hash-list(1), a User Command and honestly? a little icon. it's the tool that takes your openssl certs and turns them into EFI signature hash revocation lists. yes the name is a mouthful, no we're not changing it. iykyk π
β¨ SYNOPSIS β¨
cert-to-efi-hash-list [-g <guid>][-t <timestamp>][-s <hash>] <crt file>
<efi sig list file>
that's it. that's the whole vibe check. two files in, magic out. π¦
πΈ DESCRIPTION πΈ
so here's the tea: you hand it an input X509 certificate (in PEM format, obviously, we're not animals) and it converts it into an EFI signature hash list file. and the file contains only that single certificate. one cert, one list, no cap. π
it's giving "lowkey simple but highkey important." main character energy fr fr.
π OPTIONS π
-g <guid>β use<guid>as the owner of the signature. this is your little name tag for the key. and if you don't supply it? bestie, you get an all zero guid. (yes, literally all zeros. the beige of guids. π)-s <hash>β use the SHA<hash> hash algorithm. valid values are256,384,512. pick your fighter. β-t <timestamp>β the time of Revocation for the hash signature. and here's the important bit: set it to0if not specified, which means revoke for all time. periodt. π₯
β οΈ ngl this one matters: signature revocation hashes are only implemented in UEFI 2.4 and up. so if your firmware is older than that, this whole thing is gonna be a no from it. π
π§ EXAMPLES π§
converting a cert, the classic π
to take a standard X509 certificate in PEM format and produce an output EFI signature list file, simply do:
cert-to-efi-hash-list PK.crt PK.esl
slay. done. you ate. π
stacking them up π«Ά
note that the format of EFI signature list files is such that they can simply be concatenated to produce a file with multiple signatures:
cat PK1.esl PK2.esl > PK.esl
literally just cat them together. they're built different (built compatible). π
the guid glow-up β¨
so if your platform has a setup mode key manipulation ability, the keys will often only be displayed by GUID. which means if you're planning to manage lots of keys, using the -g option to give your keys recognisable GUIDs will be useful. do future-you a solid, bestie. π
π SEE ALSO π
sign-efi-sig-list(1) β for details on how to create an authenticated update to EFI secure variables when the EFI system is in user mode. go read it, it's the sequel. π
okay that's the whole page!! no sections skipped, no flags dropped, we keep every detail around here π
this was cert-to-efi-hash-list version 1.9.2, dated August 2025 β so basically recent, so basically relevant. mwah, go forth and hash π§ππΈ
π¦ where this page comes from
- alpine 3.23: efitools-doc 1.9.2-r13 Β· (GPL-2.0-only AND LGPL-2.1-or-later) WITH OpenSSL-Exception
- alpine 3.24: efitools-doc 1.9.2-r13 Β· (GPL-2.0-only AND LGPL-2.1-or-later) WITH OpenSSL-Exception
- fedora 43: efitools 1.9.2-18.fc43 Β· GPL-2.0-only and LGPL-2.1-or-later and BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms