Is it possible to support chainloading of Akeo's uefi-ntfs.img module through module.ubuldr bootloader in a NTFS + FAT32 partitioned UEFI Bootable USB drive for both Secure Boot On and Off ?
i mean module.ubuldr should chainload .efi bootloaders of Win 10, Ubuntu & UEFI:NTFS for both Secure Boot Systems and Non-Secure Boot systems ? So that i will always be able to UEFI boot all above .efi bootloaders for Secure Boot Disabled systems. And for Secure UEFI systems at least Win 10 & Ubuntu .efi bootloaders will surely boot.
Secure boot requires all drivers (including NTFS driver) to be signed (or hash whitelisted). So, as ntfs_x64.efi is not signed, you will not be able to load it in Secure Boot (without manually whitelisting its hash), regardless which loader you use. When Secure Boot is disabled, you can chainload and load everything. So in case your Ubuntu and/or Win10 is on a NTFS drive, you will not be able to load it with Secure Boot enabled (without manually whitelisting the hash of the NTFS driver), since you cannot load the NTFS driver.
Normally uefi-ntfs.img does not support Secure UEFI boot. Will it secure boot if chainloading through module.ubuldr ?
No. That image is not signed either.
Sorry, I must be missing something... I am trying the usb-modboot project but I just get a rescue prompt. I seem to be missing a bunch of grub files?
[Edit] Not sure what my problem was??? When I opened the usb-modboot zip file there was no install folder and the install files were in the root. Now there is an install folder and everything is OK. 7Zip seemed to have gone crazy?? Same file that I downloaded before now shows correct contents so I really don't know what went wrong. Anyway - it boots OK now. Sorry for false alarm.
Also, where should I put payload files like Ubuntu.iso ???
It says to put 'modules' in usb-modboot folder - does this mean ISOs go in here too?
ReadMe mentions an 'install' directory but I can't find one (do you mean the files in the root of the USB drive?) Also it says to edit the menu.ini file - but I can't see one and no mention of what directory it is supposed to be in?
This tells me that my skills for writing README is bad Yes, they go there too.
I mentioned 3 times in the README that ISOs of many Linux distributions are valid modules. If you have a suggestion how to make the README clearer, feel free to tell me (or send a pull request).
Edited by mihi, 4 weeks ago.