If not, you'll need to jump through hoops. Using a pre-signed boot loader, such as the popular Shim program, can be even easier than disabling Secure Boot- if your distribution provides such a program. Disabling Secure Boot is quick and enables you to easily run any EFI tool you like-but it also leaves you vulnerable to any pre-boot malware that might crop up. This page is about this final option, but both of the other options have their merits. Thus, to install your favorite Linux distribution, you must disable Secure Boot, find a Linux boot loader that's signed with Microsoft's keys, or replace your computer's standard keys with ones that you control. In fact, Microsoft's keys are the only ones that are more-or-less guaranteed to be installed in your firmware, at least on desktop and laptop computers. Most commodity PCs sold today include keys that Microsoft controls. These keys (or more precisely, their private counterparts) are used to sign boot loaders, drivers, option ROMs, and other software that the firmware runs. Secure Boot works by using a set of keys embedded in the computer's firmware. If your needs are more complex, though, you may find this page of interest. If you dual-boot Windows and a single popular Linux distribution such as Fedora or Ubuntu, you probably don't need this page, either such distributions ship with Secure Boot solutions that work reasonably well for such dual-boot configurations. If you boot nothing but Windows, chances are this page won't do you any good, except perhaps to help satisfy your curiosity about the inner workings of Secure Boot. Replacing Keys Using Your Firmware's Setup Utility.

West chester university foundation