There is no other way to deploy with secureboot, without modifying the deployed OS shim.
Thus either we fix above two bugs as well, or those targets will not have secureboot and continue to use chainloading.
Requirements for secureboot are: * create valid uefi boot entries * do not delete them * use exit 1 to boot local disk
There is no other way to deploy with secureboot, without modifying the deployed OS shim.
Thus either we fix above two bugs as well, or those targets will not have secureboot and continue to use chainloading.
Requirements for secureboot are:
* create valid uefi boot entries
* do not delete them
* use exit 1 to boot local disk