5 ms·
Rufus 3.17 (released Oct 2021) onwards is secure boot signed. See: https://github.com/pbatard/rufus/releases/tag/v3.17 https://github.com/pbatard/rufus/releases
by scrlk 4y ago
Rufus 3.17 (released Oct 2021) onwards is secure boot signed. See: https://github.com/pbatard/rufus/releases/tag/v3.17 https://github.com/pbatard/rufus/releases/tag/v3.17
- Sakos 4y agoHuh, interesting. I know he'd been working on it for a while and wasn't getting anywhere because of Microsoft, but apparently he finally got it working. The only real issue is getting your bootloader signed by MS. There's no other way to pass Secure Boot verification. https://github.com/pbatard/uefi-ntfs https://github.com/pbatard/uefi-ntfs Edit: https://old.reddit.com/r/sysadmin/comments/pl2jqg/creating_bootable_usb_drives_with_rufus_requires/hcb9tw6/ https://old.reddit.com/r/sysadmin/comments/pl2jqg/creating_b... This is the last time I read anything about it from the Rufus dev (which was over a year ago)
- mook 4y agoBecause it was interesting, here's a summary: • Microsoft refuses to sign GPL3 code for secure boot, because the anti-Tivoization clause is specifically designed to prevent this (the system basically tries to achieve what Tivo did, only supporting boot authorized by people with a given key). • The Rufus developer did work to get the GPL2 ntfs-3g drivers usable in UEFI. • Microsoft appears to have no issues signing that.
- Zuiii 4y agoThis is ridiculous. I hope the EU steps in and deals with microsoft's monopoly on default secure boot keys.