You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[efitools was removed from Fedora 41](https://discussion.fedoraproject.org/t/f41-secure-boot-with-only-your-own-keys/138120)
4
4
*[efitools upstream](https://web.git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git/) is unmaintained
5
5
* sbctl can generate keys and sign, but [efi-updatevar is still needed](https://github.com/Foxboron/sbctl/issues/434)
6
6
7
-
The upstream efi-updatevar was modified so that it doesn't write to the efivars filesystem directly, but converts the "auth" files to intermediate "vardata" files instead.
7
+
The upstream `efi-updatevar` was modified so that it doesn't write to the efivars filesystem directly, but converts the `*.auth` files to intermediate `*.vardata` files instead. To avoid confusion, it was also renamed to `mkefivardata`.
8
8
9
-
It is safe to copy the vardata files onto an untrusted machine as they do not contain the private key. To enroll the secureboot keys they contain, simply copy the vardata files to the appropriate file in the efivars filesystem.
9
+
It is safe to copy the `*.vardata` files onto an untrusted machine, since they do not contain the private key. To enroll keys, it is enough to copy the vardata files to the appropriate place in the efivars filesystem.
0 commit comments