Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
All release assets, including EFI executables and kernel/initramfs pairs, are signed with signify, which provides a simple method for verifying that the contents of the file are as this project intended. Once you've installed signify (that's left as an exercise, although Void Linux provides the signify package for this purpose), just download the desired assets from the ZFSBootMenu release page, download the file sha256.sig alongside it, and run:
I am pretty sure that that I am doing something incorrectly with the configuration files for the rEFInd bootloader, but everything else should be correct. However, as I write this, I barely realized did I not use the following commands recommended from the "Usage" section from the aforementioned website where I downloaded the zfs_x64.efi driver file for rEFInd:
Personally I hate keyfiles and any form of zfs unlocking automation which stores things locally (I suppose TPM cryptography is a good exception). While I use a traditional EFI /boot with systemd-boot (bootctl) I made this initramfs hook so that my machines can dynamically unlock themselves from my vault cluster with a revokable token. Not quite the same approach and if there's no networking a machine could get caught dead in the water for booting back to a password prompt, but it's good enough right now that I use it on everything.
Related posts
- A Home Router Built on Void Linux and ZFSBootMenu
- Bash Debugging
- Is It Good Practice to Back Up Data Sets Manually on Cold Storage Externals?
- Asustor Flashstor 12 Pro FS6712X - Link change - atlantic 0000:01:00.0 eth0: atlantic: link change old 0 new 10000
- Need drivers for a Dell Fusion Io drive2 card.