3 ms·
>Most people who are building their own computer are not going to be an expert in UEFI and secure boot (some may have never even heard of these things). These p
by gruez 4y ago
>Most people who are building their own computer are not going to be an expert in UEFI and secure boot (some may have never even heard of these things). These people are almost guaranteed to need to install their own OS. So if they try, and it "doesn't work", they are going to need tech support or most likely return the motherboard as defective. Thus it makes more sense to make the default permissive.
Not only that, a popular tool for creating windows USB installers[1] fails to boot if secureboot is enabled. I looked into it a few years ago and it was because it defaults to NTFS formatting if install.wim is greater than 4GB (because of FAT32 limitations), which is most windows ISOs. Most UEFI implementations don't support NTFS, so it installs a shim loader, which is unsigned and therefore fails to boot with secureboot enabled.
[1] https://rufus.ie/en/ https://rufus.ie/en/
- scrlk 4y agoRufus 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.
- vbezhenar 4y agoI never used Rufus but I prepared USB sticks few times. Here're my observations: 1. Every computer I've used supports NTFS in its UEFI. I even thought it was standard. So simplest way to create a bootable USB stick: format it with GPT, create one big enough NTFS partition and copy ISO contents inside. That's it. 2. Converting install.wim to sub-4GB chunks is trivial one command. Create one big FAT32 partition, copy all but install.wim, convert install.wim with `dism` and copy it. That's it. Much easier and faster than using some tool doing strange things with shim loaders and whatnot. Linux sticks could be created exactly the same way. UEFI is awesome.
- fathyb 4y ago> Every computer I've used supports NTFS in its UEFI. I even thought it was standard. I've never seen a motherboard supporting anything else than FAT for an UEFI partition. What is likely happening is that you're booting using a small EFI System Partition (ESP) formatted in FAT32 which contains a bootloader with an NTFS driver. It can get confusing because the EFI bootloader generally registers new boot entries for each non-ESP partition, but these are booting the ESP with the selected partition GUID.
- Akeo 4y ago> I've never seen a motherboard supporting anything else than FAT for an UEFI partition. Then you haven't used any Gigabyte, Asus or Intel motherboard for the last 5-7 years, because all the ones I tried include a native NTFS UEFI driver alongside the mandatory FAT32 UEFI driver. But, as others have pointed out, while it is definitely getting commoditized, you can't rely on NTFS being available in a UEFI firmware.
- vbezhenar 4y agoI'm pretty sure it didn't happen because I partitioned disk myself using diskpart and I did not create any small partition with bootloader or whatever. Just one 10GB NTFS partition and copy files from mounted ISO to this partition using ordinary explorer Ctrl+C, Ctrl+V. I've used that with few Asus motherboards (I prefer this brand) and one dell laptop. They were 2015+, so relatively modern, I guess.
- ThatMedicIsASpy 4y agoI'm done with boot sticks after ventoy. bought a big one and just dump multiple isos into it.