![]() The problem of in UEFI booting was an issue in ISO file, resolved on latest released ISO today : Questions about Grub, UEFI,the liveCD and the installer. Ventoy virtualizes the ISO as a cdrom device and boot it. Google for how to make an iso uefi bootable for more info. Now, that one can currently break the trust chain somewhere down the line, by inserting a malicious program at the first level where the trust stops being validated, which, incidentally, as a method (since I am NOT calling Ventoy malicious here) is very similar to what Ventoy is doing for Windows boot, is irrelevant to the matter, because one can very much conceive an OS that is being secured all the way (and, once again, if Microsoft were to start doing just that, then that would most likely mark the end of being able to use Ventoy with Windows ISOs since it would no longer be able to inject an executable that isn't signed by Microsoft as part of the boot process) and that validates the signature of every single binary it runs along the way which means that the trust chain needs to start somewhere and (as far as user providable binaries are concerned) that trust chain starts with Secure Boot. What exactly is the problem? Now, if Microsoft finally relinquished their abusive policy about not accepting GPLv3 code for Secure Boot signing and Ventoy was updated not to allow unsigned bootloaders when Secure Boot is enabled (i.e. Tested below ISOs on HP ENVY x360- 13-ag0007au (1st-gen Ryzen Mobile convertible laptop, BIOS F.46 Rev.A) with Ventoy 1.0.08 final release in UEFI secure boot mode: Nice job and thanks a lot for this neat tool! regular-cinnamon-latest-x86_64.iso - 1.1 GB, openSUSE-Tumbleweed-GNOME-Live-x86_64-Snapshot20200326-Media.iso - 852MB If so, please include aflag to stop this check from happening! to your account, Hello Maybe the image does not support X64 UEFI" hello everyone Using ventoy, if I try to install the ISO. only ventoy give error "No bootfile found for UEFI! You can put a file with name. Try updating it and see if that fixes the issue. Option1: Use current solution(Super UEFIinSecureBoot Disk), then user will be clearly told that, in this case, the secure boot will be by passed.
0 Comments
Leave a Reply. |