Jump to content

UEFI: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→{{Anchor|GOP|VARIABLE}}Services: This is not „fearmongering“. Check the reference
Line 135: Line 135:
=== {{Anchor|GOP|VARIABLE}}Services ===
=== {{Anchor|GOP|VARIABLE}}Services ===
EFI defines two types of services: ''boot services'' and ''runtime services''. Boot services are available only while the firmware owns the platform (i.e., before the <code>ExitBootServices</code> call), and they include text and graphical consoles on various devices, and bus, block and file services. Runtime services are still accessible while the operating system is running; they include services such as date, time and [[Non-volatile random-access memory|NVRAM]] access.
EFI defines two types of services: ''boot services'' and ''runtime services''. Boot services are available only while the firmware owns the platform (i.e., before the <code>ExitBootServices</code> call), and they include text and graphical consoles on various devices, and bus, block and file services. Runtime services are still accessible while the operating system is running; they include services such as date, time and [[Non-volatile random-access memory|NVRAM]] access.
<code>ExitBootServices</code> is used by the [[CIA]] as a hook to inject their trojan code even before the Operating System is loaded.<ref name="Vault7">{{cite web|url= https://puri.sm/posts/efi-uefi-proven-to-be-exploited-in-vault7/ | title=ExitBootServices Hooking |website=puri.sm |date= |accessdate=2020-03-07}}</ref>


In addition, the ''Graphics Output Protocol'' (GOP) provides limited runtime services support; see also [[#Graphics features|Graphics features]] section below. The operating system is permitted to directly write to the framebuffer provided by GOP during runtime mode. However, the ability to change video modes is lost after transitioning to runtime services mode until the OS graphics driver is loaded.
In addition, the ''Graphics Output Protocol'' (GOP) provides limited runtime services support; see also [[#Graphics features|Graphics features]] section below. The operating system is permitted to directly write to the framebuffer provided by GOP during runtime mode. However, the ability to change video modes is lost after transitioning to runtime services mode until the OS graphics driver is loaded.

Revision as of 18:46, 7 March 2020

EFI's position in the software stack

The Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the legacy Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers,[1][2] with most UEFI firmware implementations providing support for legacy BIOS services. UEFI can support remote diagnostics and repair of computers, even with no operating system installed.[3]

Intel developed the original Extensible Firmware Interface (EFI) specifications. Some of the EFI's practices and data formats mirror those of Microsoft Windows.[4][5] In 2005, UEFI deprecated EFI 1.10 (the final release of EFI). The Unified EFI Forum is the industry body that manages the UEFI specifications throughout.

History

The original motivation for EFI came during early development of the first Intel–HP Itanium systems in the mid-1990s. BIOS limitations (such as 16-bit processor mode, 1 MB addressable space and PC AT hardware) had become too restrictive for the larger server platforms Itanium was targeting.[6] The effort to address these concerns began in 1998 and was initially called Intel Boot Initiative.[7] It was later renamed to Extensible Firmware Interface (EFI).[8][9]

In July 2005, Intel ceased its development of the EFI specification at version 1.10, and contributed it to the Unified EFI Forum, which has developed the specification as the Unified Extensible Firmware Interface (UEFI). The original EFI specification remains owned by Intel, which exclusively provides licenses for EFI-based products, but the UEFI specification is owned by the UEFI Forum.[6][10]

Version 2.1 of the UEFI specification was released on 7 January 2007. It added cryptography, network authentication and the user interface architecture ('Human Interface Infrastructure' in UEFI). The latest UEFI specification, version 2.8, was approved in March 2019.[11]

Tiano was the first open source UEFI implementation and was released by Intel in 2004. Tiano has since then been superseded by EDK[12] and EDK2[13] and is now maintained by the TianoCore community.[14]

In December 2018, Microsoft announced Project Mu, a fork of TianoCore EDK2 used in Microsoft Surface and Hyper-V products. The project promotes the idea of Firmware as a Service.[15]

Advantages

The interface defined by the EFI specification includes data tables that contain platform information, and boot and runtime services that are available to the OS loader and OS. UEFI firmware provides several technical advantages over a traditional BIOS system:[16]

  • Ability to use large disks partitions (over 2 TB) with a GUID Partition Table (GPT)[17][a]
  • CPU-independent architecture[a]
  • CPU-independent drivers[a]
  • Flexible pre-OS environment, including network capability
  • Modular design
  • Backward and forward compatibility

Compatibility

Processor compatibility

As of version 2.5, processor bindings exist for Itanium, x86, x86-64, ARM (AArch32) and ARM64 (AArch64).[18] Only little-endian processors can be supported.[19] Unofficial UEFI support is under development for POWERPC64 by implementing TianoCore on top of OPAL,[20] the OpenPOWER abstraction layer, running in little-endian mode.[21] Similar projects exist for MIPS[22] and RISC-V.[23] As of UEFI 2.7, RISC-V processor bindings have been officially established for 32-, 64- and 128-bit modes.[24]

Standard PC BIOS is limited to a 16-bit processor mode and 1 MB of addressable memory space, resulting from the design based on the IBM 5150 that used a 16-bit Intel 8088 processor.[6][25] In comparison, the processor mode in a UEFI environment can be either 32-bit (x86-32, AArch32) or 64-bit (x86-64, Itanium, and AArch64).[6][26] 64-bit UEFI firmware implementations support long mode, which allows applications in the preboot execution environment to use 64-bit addressing to get direct access to all of the machine's memory.[27]

UEFI requires the firmware and operating system loader (or kernel) to be size-matched; for example, a 64-bit UEFI firmware implementation can load only a 64-bit operating system (OS) boot loader or kernel. After the system transitions from "Boot Services" to "Runtime Services", the operating system kernel takes over. At this point, the kernel can change processor modes if it desires, but this bars usage of the runtime services (unless the kernel switches back again).[28]: sections 2.3.2 and 2.3.4  As of version 3.15, the Linux kernel supports 64-bit kernels to be booted on 32-bit UEFI firmware implementations running on x86-64 CPUs, with UEFI handover support from a UEFI boot loader as the requirement.[29] UEFI handover protocol deduplicates the UEFI initialization code between the kernel and UEFI boot loaders, leaving the initialization to be performed only by the Linux kernel's UEFI boot stub.[30][31]

Disk device compatibility

See also: GPT § Operating systems support, and Protective MBR

In addition to the standard PC disk partition scheme that uses a master boot record (MBR), UEFI also works with a new partitioning scheme called GUID Partition Table (GPT), which is free from many of the limitations of MBR. In particular, the MBR limits on the number and size of disk partitions (up to four primary partitions per disk, and up to 2 TiB (2 × 240 bytes) per disk) are relaxed.[32] More specifically, GPT allows for a maximum disk and partition size of 8 ZiB (8 × 270 bytes).[33][34]

Linux

See also: EFI System partition § Linux

Support for GPT in Linux is enabled by turning on the option CONFIG_EFI_PARTITION (EFI GUID Partition Support) during kernel configuration.[35] This option allows Linux to recognize and use GPT disks after the system firmware passes control over the system to Linux.

For reverse compatibility, Linux can use GPT disks in BIOS-based systems for both data storage and booting, as both GRUB 2 and Linux are GPT-aware. Such a setup is usually referred to as BIOS-GPT.[36] As GPT incorporates the protective MBR, a BIOS-based computer can boot from a GPT disk using a GPT-aware boot loader stored in the protective MBR's bootstrap code area.[34] In the case of GRUB, such a configuration requires a BIOS boot partition for GRUB to embed its second-stage code due to absence of the post-MBR gap in GPT partitioned disks (which is taken over by the GPT's Primary Header and Primary Partition Table). Commonly 1 MiB in size, this partition's Globally Unique Identifier (GUID) in GPT scheme is 21686148-6449-6E6F-744E-656564454649 and is used by GRUB only in BIOS-GPT setups. From GRUB's perspective, no such partition type exists in case of MBR partitioning. This partition is not required if the system is UEFI-based because no embedding of the second-stage code is needed in that case.[17][34][36]

UEFI systems can access GPT disks and boot directly from them, which allows Linux to use UEFI boot methods. Booting Linux from GPT disks on UEFI systems involves creation of an EFI system partition (ESP), which contains UEFI applications such as bootloaders, operating system kernels, and utility software.[37][38][39] Such a setup is usually referred to as UEFI-GPT, while ESP is recommended to be at least 512 MiB in size and formatted with a FAT32 filesystem for maximum compatibility.[34][36][40]

For backward compatibility, most UEFI implementations also support booting from MBR-partitioned disks, through the Compatibility Support Module (CSM) that provides legacy BIOS compatibility.[41] In that case, booting Linux on UEFI systems is the same as on legacy BIOS-based systems.

Microsoft Windows

The 64-bit versions of Windows Vista SP1 and later can boot from disks with a partition size larger than 2 TB.

Features

Services

EFI defines two types of services: boot services and runtime services. Boot services are available only while the firmware owns the platform (i.e., before the ExitBootServices call), and they include text and graphical consoles on various devices, and bus, block and file services. Runtime services are still accessible while the operating system is running; they include services such as date, time and NVRAM access. ExitBootServices is used by the CIA as a hook to inject their trojan code even before the Operating System is loaded.[42]

In addition, the Graphics Output Protocol (GOP) provides limited runtime services support; see also Graphics features section below. The operating system is permitted to directly write to the framebuffer provided by GOP during runtime mode. However, the ability to change video modes is lost after transitioning to runtime services mode until the OS graphics driver is loaded.

Variable services
UEFI variables provide a way to store data, in particular non-volatile data, that is shared between platform firmware and operating systems or UEFI applications. Variable namespaces are identified by GUIDs, and variables are key/value pairs. For example, variables can be used to keep crash messages in NVRAM after a crash for the operating system to retrieve after a reboot.[43]
Time services
UEFI provides device-independent time services. Time services include support for timezone and daylight saving fields, which allow the hardware real-time clock to be set to local time or UTC.[44] On machines using a PC-AT real-time clock, by default the hardware clock still has to be set to local time for compatibility with BIOS-based Windows,[5] unless using recent versions and an entry in the Windows registry is set to indicate the use of UTC.

Applications

Interaction between the EFI boot manager and EFI drivers

Beyond loading an OS, UEFI can run UEFI applications, which reside as files on the EFI System Partition. They can be executed from the UEFI command shell, by the firmware's boot manager, or by other UEFI applications. UEFI applications can be developed and installed independently of the system manufacturer.

A type of UEFI application is an OS loader such as GRUB, rEFInd, Gummiboot, and Windows Boot Manager; which loads an OS file into memory and executes it. Also, an OS loader can provide a user interface to allow the selection of another UEFI application to run. Utilities like the UEFI shell are also UEFI applications.

Protocols

EFI defines protocols as a set of software interfaces used for communication between two binary modules. All EFI drivers must provide services to others via protocols.

Device drivers

In addition to standard processor architecture-specific device drivers, EFI provides for a processor-independent device driver stored in memory as EFI byte code or EBC. System firmware has an interpreter for EBC images. In that sense, EBC is analogous to Open Firmware, the hardware-independent firmware used in PowerPC-based Apple Macintosh and Sun Microsystems SPARC computers, among others.

Some architecture-specific (non-EFI Byte Code) EFI drivers for some device types can have interfaces for use by the OS. This allows the OS to rely on EFI for drivers to perform basic graphics and network functions before, and if, operating-system-specific drivers are loaded.

Graphics features

The EFI specification defined a UGA (Universal Graphic Adapter) protocol as a way to support device-independent graphics. UEFI did not include UGA and replaced it with GOP (Graphics Output Protocol), with the explicit goal of removing VGA hardware dependencies. The two are similar.[45]

UEFI 2.1 defined a "Human Interface Infrastructure" (HII) to manage user input, localized strings, fonts, and forms (in the HTML sense). These enable original equipment manufacturers (OEMs) or independent BIOS vendors (IBVs) to design graphical interfaces for pre-boot configuration; UEFI itself does not define a user interface.

Most early UEFI firmware implementations were console-based, but as early as 2007 some implementations featured a graphical user interface.

EFI system partition

Main article: EFI system partition

An EFI system partition, often abbreviated to ESP, is a data storage device partition that is used in computers adhering to the UEFI specification. Accessed by the UEFI firmware when a computer is powered up, it stores UEFI applications and the files these applications need to run, including operating system kernels. Supported partition table schemes include MBR and GPT, as well as El Torito volumes on optical disks.[28]: section 2.6.2  For use on ESPs, UEFI defines a specific version of the FAT file system, which is maintained as part of the UEFI specification and independently from the original FAT specification, encompassing a variant of the FAT32 file system on ESPs, and FAT16 and FAT12 file systems on removable media.[28]: section 12.3 [46][47] The ESP also provides space for a boot sector as part of the backward BIOS compatibility.[41]

Booting

UEFI booting

Unlike the legacy PC BIOS, UEFI does not rely on a boot sector, defining instead a boot manager as part of the UEFI specification. When a computer is powered on, the boot manager checks the boot configuration and based on its settings, loads into memory and then executes the specified OS loader or operating system kernel. The boot configuration is defined by variables stored in NVRAM, including variables that indicate the file system paths to OS loaders and OS kernels.

OS loaders can be automatically detected by UEFI, which enables easy booting from removable devices such as USB flash drives. This automated detection relies on standardized file paths to the OS loader, with the path varying depending on the computer architecture. The format of the file path is defined as <EFI_SYSTEM_PARTITION>/EFI/BOOT/BOOT<MACHINE_TYPE_SHORT_NAME>.EFI; for example, the file path to the OS loader on an x86-64 system is /efi/BOOT/BOOTX64.EFI,[28] and efi\boot\bootaa64.efi on ARM64 architecture.

Booting UEFI systems from GPT-partitioned disks is commonly called UEFI-GPT booting. Despite the fact that the UEFI specification requires MBR partition tables to be fully supported,[28] some UEFI firmware implementations immediately switch to the BIOS-based CSM booting depending on the type of boot disk's partition table, effectively preventing UEFI booting to be performed from EFI System partitions on MBR-partitioned disks.[41] Such a boot scheme is commonly called UEFI-MBR.

It is also common for a boot manager to have a textual user interface so the user can select the desired OS (or system utility) from a list of available boot options.

CSM booting

To ensure backward compatibility, most UEFI firmware implementations on PC-class machines also support booting in legacy BIOS mode from MBR-partitioned disks, through the Compatibility Support Module (CSM) that provides legacy BIOS compatibility. In this scenario, booting is performed in the same way as on legacy BIOS-based systems, by ignoring the partition table and relying on the content of a boot sector.[41]

BIOS-style booting from MBR-partitioned disks is commonly called BIOS-MBR, regardless of it being performed on UEFI or legacy BIOS-based systems. Furthermore, booting legacy BIOS-based systems from GPT disks is also possible, and such a boot scheme is commonly called BIOS-GPT.

The Compatibility Support Module allows legacy operating systems and some option ROMs that do not support UEFI to still be used.[48] It also provides required legacy System Management Mode (SMM) functionality, called CompatibilitySmm, as an addition to features provided by the UEFI SMM. This is optional and highly chipset- and platform-specific. An example of such a legacy SMM functionality is providing USB legacy support for keyboard and mouse, by emulating their classic PS/2 counterparts.[48]

In November 2017, Intel announced that it planned to phase out support for CSM by 2020.[49]

Network booting

The UEFI specification includes support for booting over network via the Preboot eXecution Environment (PXE). PXE booting use network protocols include Internet Protocol (IPv4 and IPv6), User Datagram Protocol (UDP), Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol (TFTP).[28][50]

OS images can be remotely stored on storage area networks (SANs), with Internet Small Computer System Interface (iSCSI) and Fibre Channel over Ethernet (FCoE) as supported protocols for accessing the SANs.[28][51][52]

Version 2.5 of the UEFI specification adds support for accessing boot images over the HTTP protocol.[53]

Secure boot

See also: Secure boot criticism

The UEFI 2.3.1 Errata C specification (or higher) defines a protocol known as secure boot, which can secure the boot process by preventing the loading of drivers or OS loaders that are not signed with an acceptable digital signature. The mechanical details of how precisely these drivers are to be signed are not specified.[54] When secure boot is enabled, it is initially placed in "setup" mode, which allows a public key known as the "platform key" (PK) to be written to the firmware. Once the key is written, secure boot enters "User" mode, where only drivers and loaders signed with the platform key can be loaded by the firmware. Additional "key exchange keys" (KEK) can be added to a database stored in memory to allow other certificates to be used, but they must still have a connection to the private portion of the platform key.[55] Secure boot can also be placed in "Custom" mode, where additional public keys can be added to the system that do not match the private key.[56]

Secure boot is supported by Windows 8 and 8.1, Windows Server 2012, and 2012 R2, and Windows 10, VMware vSphere 6.5[57] and a number of Linux distributions including Fedora (since version 18), openSUSE (since version 12.3), RHEL (since version 7), CentOS (since version 7[58]), Debian (since version 10),[59] and Ubuntu (since version 12.04.2).[60] As of January 2017, FreeBSD support is in a planning stage.[61]

UEFI shell

UEFI provides a shell environment, which can be used to execute other UEFI applications, including UEFI boot loaders.[39] Apart from that, commands available in the UEFI shell can be used for obtaining various other information about the system or the firmware, including getting the memory map (memmap), modifying boot manager variables (bcfg), running partitioning programs (diskpart), loading UEFI drivers, and editing text files (edit).[62][63][64]

Source code for a UEFI shell can be downloaded from the Intel's TianoCore UDK2010 / EDK2 SourceForge project.[65] Shell v2 works best in UEFI 2.3+ systems and is recommended over the shell v1 in those systems. Shell v1 should work in all UEFI systems.[62][66][67]

Methods used for launching UEFI shell depend on the manufacturer and model of the system motherboard. Some of them already provide a direct option in firmware setup for launching, e.g. compiled x86-64 version of the shell needs to be made available as <EFI_SYSTEM_PARTITION>/SHELLX64.EFI. Some other systems have an already embedded UEFI shell which can be launched by appropriate key press combinations.[68][69] For other systems, the solution is either creating an appropriate USB flash drive or adding manually (bcfg) a boot option associated with the compiled version of shell.[64][68][70][71]

Commands

The following list of commands is supported by the EFI shell.[63]

Extensions

Extensions to EFI can be loaded from virtually any non-volatile storage device attached to the computer. For example, an original equipment manufacturer (OEM) can distribute systems with an EFI partition on the hard drive, which would add additional functions to the standard EFI firmware stored on the motherboard's ROM.

UEFI classes

UEFI machines can have one of the following "classes", which were used to help ease the transition to UEFI.

  • Class 0:Legacy BIOS
  • Class 1:Legacy BIOS with UEFI code, although it does not support UEFI booting
  • Class 2:UEFI with CSM
  • Class 3:UEFI without CSM

Boot stages

SEC - Security Phase

This is the first stage of the UEFI boot but may have platform specific binary code that precedes it. (EX. Intel ME, AMD PSP). Minimal code written in assembly for the specific architecture. It initializes a temporary memory (often CPU cache as RAM) and serves as the systems software root of trust with the option of verifying PEI before hand-off.

PEI - Pre-EFI Initialization

The second stage of UEFI boot consist of a dependency aware dispatcher that loads and runs C written modules (PEIMs) to handle early hardware initialization tasks such as memory initialization and recovery operations. Additionally it is responsible for discovery of the current boot mode and handling many S3 operations. In the case of S3 resume, it is responsible for restoring many hardware registers to a pre-sleep state.

DXE - Driver Execution Environment

This stage also consist of C modules and a dependency aware dispatcher. With memory now available, most hardware drivers, feature code, PCI bus, and runtime services (UEFI -> OS services) are initialized.

BDS - Boot Device Select

In this stage, input and output devices are typically initialized, drivers or OPROMs on PCI devices are executed according to system configuration, and boot options are processed for availability, ordering, and device matching.

TSL - Transient System Load

This is the stage between boot selection and hand-off to the OS. At this point one may enter setup, UEFI shell, or execute an EFI application such as the OS boot loader.

RT - Runtime

The UEFI hands off to the OS. A UEFI compatible OS is now responsible for exiting boot services triggering the firmware to unload all no longer needed code and data leaving only SMM and Runtime service code / data.

When a legacy OS is used, CSM will handle this call ensuring the system is compatible with legacy BIOS expectations.

Implementation and adoption

Intel EFI

Intel's implementation of EFI is the Intel Platform Innovation Framework, codenamed Tiano. Tiano runs on Intel's XScale, Itanium and IA-32 processors, and is proprietary software, although a portion of the code has been released under the BSD license or Eclipse Public License (EPL) as TianoCore. TianoCore can be used as a payload for coreboot.[72]

Phoenix Technologies' implementations of UEFI include its SecureCore and SecureCore Tiano products.[73] American Megatrends offers its own UEFI firmware implementation known as Aptio,[74] while Insyde Software offers InsydeH2O, its own implementation of Tiano.[75]

In December 2018, Microsoft released an open source version of its TianoCore EDK2-based UEFI implementation from the Surface line, Project Mu.[76]

Das U-Boot

An implementation of the UEFI API was introduced into the Universal Boot Loader (Das U-Boot) in 2017.[77] On the ARMv8 architecture Linux distributions use the U-Boot UEFI implementation in conjunction with GNU GRUB for booting (e.g. SUSE Linux [78]), the same holds true for OpenBSD.[79] For booting from iSCSI iPXE can be used as a UEFI application loaded by U-Boot.[80]

Platforms using EFI/UEFI

Intel's first Itanium workstations and servers, released in 2000, implemented EFI 1.02.

Hewlett-Packard's first Itanium 2 systems, released in 2002, implemented EFI 1.10; they were able to boot Windows, Linux, FreeBSD and HP-UX; OpenVMS added UEFI capability in June 2003.

In January 2006, Apple Inc. shipped its first Intel-based Macintosh computers. These systems used EFI instead of Open Firmware, which had been used on its previous PowerPC-based systems.[81] On 5 April 2006, Apple first released Boot Camp, which produces a Windows drivers disk and a non-destructive partitioning tool to allow the installation of Windows XP or Vista without requiring a reinstallation of Mac OS X. A firmware update was also released that added BIOS compatibility to its EFI implementation. Subsequent Macintosh models shipped with the newer firmware.[82]

During 2005, more than one million Intel systems shipped with Intel's implementation of UEFI.[83] New mobile, desktop and server products, using Intel's implementation of UEFI, started shipping in 2006. For instance, boards that use the Intel 945 chipset series use Intel's UEFI firmware implementation.

Since 2005, EFI has also been implemented on non-PC architectures, such as embedded systems based on XScale cores.[83]

The EDK (EFI Developer Kit) includes an NT32 target, which allows EFI firmware and EFI applications to run within a Windows application. But no direct hardware access is allowed by EDK NT32. This means only a subset of EFI application and drivers can be executed at the EDK NT32 target.

In 2008, more x86-64 systems adopted UEFI some of them using the rEFInd GUI boot menu. While many of these systems still allow booting only the BIOS-based OSes via the Compatibility Support Module (CSM) (thus not appearing to the user to be UEFI-based), other systems started to allow booting UEFI-based OSes. For example, IBM x3450 server, MSI motherboards with ClickBIOS, all HP EliteBook Notebook and Tablet PCs, newer HP Compaq Notebook PCs (e.g., 6730b, 6735b, etc.).

In 2009, IBM shipped System x machines (x3550 M2, x3650 M2, iDataPlex dx360 M2) and BladeCenter HS22 with UEFI capability. Dell shipped PowerEdge T610, R610, R710, M610 and M710 servers with UEFI capability. More commercially available systems are mentioned in a UEFI whitepaper.[84]

In 2011, major vendors (such as ASRock, Asus, Gigabyte, and MSI) launched several consumer-oriented motherboards using the Intel 6-series LGA 1155 chipset and AMD 9 Series AM3+ chipsets with UEFI.[85]

With the release of Windows 8 in October 2012, Microsoft's certification requirements now require that computers include firmware that implements the UEFI specification. Furthermore, if the computer supports the "Connected Standby" feature of Windows 8 (which allows devices to have power management comparable to smartphones, with an almost instantaneous return from standby mode), then the firmware is not permitted to contain a Compatibility Support Module (CSM). As such, systems that support Connected Standby are incapable of booting Legacy BIOS operating systems.[86][87]

In October 2017, Intel announced that it would remove legacy PC BIOS support from all its products by 2020, in favor of UEFI Class 3.[88]

Operating systems

An operating system that can be booted from a (U)EFI is called a (U)EFI-aware operating system, defined by (U)EFI specification. Here the term booted from a (U)EFI means directly booting the system using a (U)EFI operating system loader stored on any storage device. The default location for the operating system loader is <EFI_SYSTEM_PARTITION>/BOOT/BOOT<MACHINE_TYPE_SHORT_NAME>.EFI, where short name of the machine type can be IA32, X64, IA64, ARM or AA64.[28] Some operating systems vendors may have their own boot loaders. They may also change the default boot location.

  • The Linux kernel has been able to use EFI at boot time since early 2000,[89] using the elilo EFI boot loader or, more recently, EFI versions of GRUB.[90] Grub+Linux also supports booting from a GUID partition table without UEFI.[17] The distribution Ubuntu added support for UEFI secure boot as of version 12.10.[91] Furthermore, the Linux kernel can be compiled with the option to run as an EFI bootloader on its own through the EFI bootstub feature.
  • HP-UX has used (U)EFI as its boot mechanism on IA-64 systems since 2002.
  • HP OpenVMS has used (U)EFI on IA-64 since its initial evaluation release in December 2003, and for production releases since January 2005.[92]
  • Apple uses EFI for its line of Intel-based Macs. Mac OS X v10.4 Tiger and Mac OS X v10.5 Leopard implement EFI v1.10 in 32-bit mode even on newer 64-bit CPUs, but full support arrived with OS X v10.8 Mountain Lion.[93]
  • The Itanium versions of Windows 2000 (Advanced Server Limited Edition and Datacenter Server Limited Edition) implemented EFI 1.10 in 2002. MS Windows Server 2003 for IA-64, MS Windows XP 64-bit Edition and Windows 2000 Advanced Server Limited Edition, all of which are for the Intel Itanium family of processors, implement EFI, a requirement of the platform through the DIG64 specification.[94]
  • Microsoft introduced UEFI for x86-64 Windows operating systems with Windows Server 2008 R2 and Windows 7. The 64-bit versions of Windows 7 are compatible with EFI.[citation needed] 32-bit UEFI was originally not supported since vendors did not have any interest in producing native 32-bit UEFI firmware because of the mainstream status of 64-bit computing.[95] Windows 8 includes further optimizations for UEFI systems, including a faster startup, 32-bit UEFI support, and secure boot support.[96][97]
  • On 5 March 2013, the FreeBSD Foundation awarded a grant to a developer seeking to add UEFI support to the FreeBSD kernel and bootloader.[98] The changes were initially stored in a discrete branch of the FreeBSD source code, but were merged into the mainline source on 4 April 2014 (revision 264095); the changes include support in the installer as well.[99]
  • Oracle Solaris 11.1 and later support UEFI boot for x86 systems with UEFI firmware version 2.1 or later. GRUB 2 is used as the boot loader on x86.[100]
  • OpenBSD 5.9[101] introduced UEFI boot support for 64-bit x86 systems using its own custom loader, OpenBSD 6.0 extended that support to include ARMv7.[102]

Use of UEFI with virtualization

  • HP Integrity Virtual Machines provides UEFI boot on HP Integrity Servers. It also provides a virtualized UEFI environment for the guest UEFI-aware OSes.
  • Intel hosts an Open Virtual Machine Firmware project on SourceForge.[103]
  • VMware Fusion 3 software for Mac OS X can boot Mac OS X Server virtual machines using UEFI.
  • VMware Workstation prior to version 11 unofficially supports UEFI, but is manually enabled by editing the .vmx file.[104] VMware Workstation version 11 and above supports UEFI, independently of whether the physical host system is UEFI-based. VMware Workstation 14 (and accordingly, Fusion 10) adds support for the Secure Boot feature of UEFI.[105][106]
  • The vSphere ESXi 5.0 hypervisor officially support UEFI. Version 6.5 adds support for secure boot.[107][108]
  • VirtualBox has implemented UEFI since 3.1,[109] but limited to Unix/Linux operating systems and some versions of Windows (does not work with Windows Vista x64 and Windows 7 x64).[110][111]
  • QEMU/KVM can be used with the Open Virtual Machine Firmware (OVMF) provided by TianoCore.[112]
  • The VMware ESXi version 5 hypervisor, part of VMware vSphere, supports virtualized UEFI as an alternative to the legacy PC BIOS inside a virtual machine.
  • The second generation of the Microsoft Hyper-V virtual machine supports virtualized UEFI.[113]
  • Google Cloud Platform Shielded VMs support virtualized UEFI to enable Secure Boot.[114]

Applications development

EDK2 Application Development Kit (EADK) makes it possible to use standard C library functions in UEFI applications. EADK can be freely downloaded from the Intel's TianoCore UDK2010 / EDK2 SourceForge project. As an example, a port of the Python interpreter is made available as a UEFI application by using the EADK.[115]

A minimalistic "hello, world" C program written using EADK looks similar to its usual C counterpart: 

#include <Uefi.h>
#include <Library/UefiLib.h>
#include <Library/ShellCEntryLib.h>

EFI_STATUS EFIAPI ShellAppMain(IN UINTN Argc, IN CHAR16 **Argv)
{
    Print(L"hello, world\n");
    return EFI_SUCCESS;
}

Criticism

Numerous digital rights activists have protested against UEFI. Ronald G. Minnich, a co-author of coreboot, and Cory Doctorow, a digital rights activist, have criticized EFI as an attempt to remove the ability of the user to truly control the computer.[116][117] It does not solve the BIOS's long-standing problems of requiring two different drivers—one for the firmware and one for the operating system—for most hardware.[118]

Open-source project TianoCore also provides UEFI interfaces.[119] TianoCore lacks the specialized drivers that initialize chipset functions, which are instead provided by coreboot, of which TianoCore is one of many payload options. The development of coreboot requires cooperation from chipset manufacturers to provide the specifications needed to develop initialization drivers.

Secure boot

See also: Windows 8 § Reception

In 2011, Microsoft announced that computers certified to run its Windows 8 operating system had to ship with Microsoft's public key enrolled and secure boot enabled. Following the announcement, the company was accused by critics and free software/open source advocates (including the Free Software Foundation) of trying to use the secure boot functionality of UEFI to hinder or outright prevent the installation of alternative operating systems such as Linux. Microsoft denied that the secure boot requirement was intended to serve as a form of lock-in, and clarified its requirements by stating that x86-based systems certified for Windows 8 must allow secure boot to enter custom mode or be disabled, but not on systems using the ARM architecture.[56][120] Windows 10 allows OEMs to decide whether or not secure boot can be managed by users of their x86 systems.[121]

Other developers raised concerns about the legal and practical issues of implementing support for secure boot on Linux systems in general. Former Red Hat developer Matthew Garrett noted that conditions in the GNU General Public License version 3 may prevent the use of the GNU Grand Unified Bootloader without a distribution's developer disclosing the private key (however, the Free Software Foundation has since clarified its position, assuring that the responsibility to make keys available was held by the hardware manufacturer),[91] and that it would also be difficult for advanced users to build custom kernels that could function with secure boot enabled without self-signing them.[120] Other developers suggested that signed builds of Linux with another key could be provided, but noted that it would be difficult to persuade OEMs to ship their computers with the required key alongside the Microsoft key.[2]

Several major Linux distributions have developed different implementations for secure boot. Garrett himself developed a minimal bootloader known as a shim, which is a precompiled, signed bootloader that allows the user to individually trust keys provided by distributors.[122] Ubuntu 12.10 uses an older version of shim[which?] pre-configured for use with Canonical's own key that verifies only the bootloader and allows unsigned kernels to be loaded; developers believed that the practice of signing only the bootloader is more feasible, since a trusted kernel is effective at securing only the user space, and not the pre-boot state for which secure boot is designed to add protection. That also allows users to build their own kernels and use custom kernel modules as well, without the need to reconfigure the system.[91][123][124] Canonical also maintains its own private key to sign installations of Ubuntu pre-loaded on certified OEM computers that run the operating system, and also plans to enforce a secure boot requirement as well—requiring both a Canonical key and a Microsoft key (for compatibility reasons) to be included in their firmware. Fedora also uses shim,[which?] but requires that both the kernel and its modules be signed as well.[123]

It has been disputed whether the kernel and its modules must be signed as well; while the UEFI specifications do not require it, Microsoft has asserted that their contractual requirements do, and that it reserves the right to revoke any certificates used to sign code that can be used to compromise the security of the system.[124] In February 2013, another Red Hat developer attempted to submit a patch to the Linux kernel that would allow it to parse Microsoft's authenticode signing using a master X.509 key embedded in PE files signed by Microsoft. However, the proposal was criticized by Linux creator Linus Torvalds, who attacked Red Hat for supporting Microsoft's control over the secure boot infrastructure.[125]

On 26 March 2013, the Spanish free software development group Hispalinux filed a formal complaint with the European Commission, contending that Microsoft's secure boot requirements on OEM systems were "obstructive" and anti-competitive.[126]

At the Black Hat conference in August 2013, a group of security researchers presented a series of exploits in specific vendor implementations of UEFI that could be used to exploit secure boot.[127]

In August 2016 it was reported that two security researchers had found the "golden key" security key Microsoft uses in signing operating systems.[128] Technically, no key was exposed, however, an exploitable binary signed by the key was. This allows any software to run as though it was genuinely signed by Microsoft and exposes the possibility of rootkit and bootkit attacks. This also makes patching the fault impossible, since any patch can be replaced (downgraded) by the (signed) exploitable binary. Microsoft responded in a statement that the vulnerability only exists in ARM architecture and Windows RT devices, and has released two patches; however, the patches do not (and cannot) remove the vulnerability, which would require key replacements in end user firmware to fix.[citation needed]

Firmware problems

The increased prominence of UEFI firmware in devices has also led to a number of technical problems blamed on their respective implementations.[129]

Following the release of Windows 8 in late 2012, it was discovered that certain Lenovo computer models with secure boot had firmware that was hardcoded to allow only executables named "Windows Boot Manager" or "Red Hat Enterprise Linux" to load, regardless of any other setting.[130] Other problems were encountered by several Toshiba laptop models with secure boot that were missing certain certificates required for its proper operation.[129]

In January 2013, a bug surrounding the UEFI implementation on some Samsung laptops was publicized, which caused them to be bricked after installing a Linux distribution in UEFI mode. While potential conflicts with a kernel module designed to access system features on Samsung laptops were initially blamed (also prompting kernel maintainers to disable the module on UEFI systems as a safety measure), Matthew Garrett discovered that the bug was actually triggered by storing too many UEFI variables to memory, and that the bug could also be triggered under Windows under certain conditions. In conclusion, he determined that the offending kernel module had caused kernel message dumps to be written to the firmware, thus triggering the bug.[43][131][132]

See also

Notes

  1. ^ a b c Large disk support and features such as Advanced Configuration and Power Interface (ACPI) and System Management BIOS (SMBIOS) were subsequently implemented in BIOS-based systems.

References

  1. ^ Kinney, Michael (1 September 2000). "Solving BIOS Boot Issues with EFI" (PDF). pp. 47–50. Retrieved 14 September 2010.
  2. ^ a b "MS denies secure boot will exclude Linux". The Register. 23 September 2011. Retrieved 24 September 2011.
  3. ^ "The 30-year-long Reign of BIOS is Over: Why UEFI W... - Input Output". HP.com. Archived from the original on 26 June 2013. Retrieved 6 March 2012.
  4. ^ IBM PC Real Time Clock should run in UT. Cl.cam.ac.uk. Retrieved on 30 October 2013.
  5. ^ a b Garrett, Matthew (19 January 2012). "EFI and Linux: The Future Is Here, and It's Awful". linux.conf.au 2012. Retrieved 2 April 2012.
  6. ^ a b c d "Emulex UEFI Implementation Delivers Industry-leading Features for IBM Systems" (PDF). Emulex. Retrieved 14 September 2010.
  7. ^ Extensible Firmware Interface (EFI) and Unified EFI (UEFI), Intel, archived from the original on 5 January 2010
  8. ^ Wei, Dong (2006), "foreword", Beyond BIOS, Intel Press, ISBN 978-0-9743649-0-2
  9. ^ "1.10 Specification overview", Extensible Firmware Interface, Intel
  10. ^ About, Unified EFI Forum, Q: What is the relationship between EFI and UEFI? A: The UEFI specification is based on the EFI 1.10 specification published by Intel with corrections and changes managed by the Unified EFI Forum. Intel still holds the copyright on the EFI 1.10 specification, but has contributed it to the Forum so that the Forum can evolve it. There will be no future versions of the EFI specification, but customers who license it can still use it under the terms of their license from Intel. The license to the Unified EFI Specification comes from the Forum, not from Intel
  11. ^ "Unified Extensible Firmware Interface Forum Specifications". Retrieved 3 June 2019.
  12. ^ "GitHub - tianocore/Edk: Git mirror of EDK". 19 March 2019.
  13. ^ "GitHub - tianocore/Tianocore.github.io: Tianocore website". 8 August 2019.
  14. ^ "What is TianoCore?".
  15. ^ "Microsoft announces Project Mu, an open-source release of the UEFI core". 20 December 2018.
  16. ^ "UEFI and Windows". Microsoft. 15 September 2009. Retrieved 14 September 2010.
  17. ^ a b c "Installation". 3.4 BIOS installation. GNU GRUB. Retrieved 25 September 2013.
  18. ^ UEFI Specification 2.4, section 2.3
  19. ^ UEFI specification 2.3.1, section 1.8.1.
  20. ^ "GitHub - andreiw/ppc64le-edk2: TianoCore UEFI for OPAL/PowerNV (PPC64/PowerPC64 Little-Endian)". GitHub.
  21. ^ "Tianocore for OpenPOWER". Firmware Security. 12 October 2015.
  22. ^ kontais. "EFI-MIPS". SourceForge.
  23. ^ "lowRISC · lowRISC".
  24. ^ http://www.uefi.org/sites/default/files/resources/UEFI_Spec_2_7.pdf
  25. ^ Hardwidge, Ben (1 June 2010). "LBA explained — Solving the 3TB Problem?". bit-tech. Retrieved 18 June 2010.
  26. ^ Brian Richardson (10 May 2010). "Ask a BIOS Guy: "Why UEFI"". Intel Architecture Blog. Archived from the original on 9 October 2010. Retrieved 18 June 2010.
  27. ^ Gary Simpson. "UEFI Momentum — The AMD perspective". AMD. Archived from the original (PPTX) on 4 January 2014. Retrieved 20 September 2014.
  28. ^ a b c d e f g h "UEFI Specifications (version 2.4 and older)" (PDF). Unified EFI, Inc. June 2013. Retrieved 25 September 2013.
  29. ^ "Linux kernel 3.15, Section 1.3. EFI 64-bit kernels can be booted from 32-bit firmware". kernelnewbies.org. 8 June 2014. Retrieved 15 June 2014.
  30. ^ "x86, efi: Handover Protocol". LWN.net. 19 July 2012. Retrieved 15 June 2014.
  31. ^ "Linux kernel documentation: Documentation/efi-stub.txt". kernel.org. 1 February 2014. Retrieved 15 June 2014.
  32. ^ "FAQ: Drive Partition Limits" (PDF). UEFI Forum. Retrieved 5 December 2019.
  33. ^ "FAQ: Drive Partition Limits" (PDF). UEFI Forum. Retrieved 9 June 2010.
  34. ^ a b c d Roderick W. Smith (3 July 2012). "Make the most of large drives with GPT and Linux". IBM. Retrieved 25 September 2013.
  35. ^ "block/partitions/Kconfig (3.11.1)". CONFIG_EFI_PARTITION (line #247). kernel.org. Retrieved 25 September 2013.
  36. ^ a b c "GRUB". BIOS systems. Arch Linux. Retrieved 25 September 2013.[unreliable source?]
  37. ^ "GRUB and the boot process on UEFI-based x86 systems". redhat.com. Retrieved 14 November 2013.
  38. ^ "UEFI Booting 64-bit Redhat Enterprise Linux 6". fpmurphy.com. September 2010. Retrieved 14 November 2013.
  39. ^ a b "UEFI Bootloaders". archlinux.org. Retrieved 25 September 2013.[unreliable source?]
  40. ^ "Unified Extensible Firmware Interface: EFI System Partition". archlinux.org. Retrieved 25 September 2013.[unreliable source?]
  41. ^ a b c d "UEFI system booting from MBR partition table and GRUB legacy". Arch Linux Forums. June 2012. Retrieved 6 October 2013.
  42. ^ "ExitBootServices Hooking". puri.sm. Retrieved 7 March 2020.
  43. ^ a b "Samsung UEFI bug: Notebook bricked from Windows". The H. Retrieved 27 February 2013.
  44. ^ UEFI specification, section 7.3
  45. ^ "Intel Embedded Graphics Drivers FAQ: BIOS and firmware". Intel. Retrieved 19 May 2014.
  46. ^ "UEFI Specification Version 2.5, Section 12.3 File System Format" (PDF). uefi.org. April 2015. pp. 536, 537. Retrieved 29 May 2015. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI defines a specific version of FAT that is explicitly documented and testable. Conformance to the EFI specification and its associate reference documents is the only definition of FAT that needs to be implemented to support EFI. To differentiate the EFI file system from pure FAT, a new partition file system type has been defined.
  47. ^ "Technical Note TN2166: Secrets of the GPT". developer.apple.com. 6 November 2006. Retrieved 6 May 2015.
  48. ^ a b "Intel® Platform Innovation Framework for EFI" (PDF). Compatibility Support Module Specification (revision 0.97). Intel. 4 September 2007. Retrieved 6 October 2013.
  49. ^ "The PC BIOS will be killed off by 2020 as Intel plans move to pure UEFI". Ars Technica. Retrieved 29 May 2018.
  50. ^ "Red Hat Enterprise Linux 6 Installation Guide". 30.2.2. Configuring PXE boot for EFI. Red Hat. Retrieved 9 October 2013.
  51. ^ El-Haj-Mahmoud, Samer (July 2013). "Advances in Pre-OS Networking in UEFI 2.4" (PDF). Hewlett-Packard. Retrieved 29 May 2019.
  52. ^ "Storage and Network Convergence Using FCoE and iSCSI" (PDF). IBM. July 2012. Retrieved 9 October 2013.
  53. ^ "New UEFI HTTP Boot support in UEFI 2.5". firmwaresecurity.com. 9 May 2015. Retrieved 13 August 2015.
  54. ^ "Secure Boot Overview". Microsoft. Retrieved 18 February 2016.
  55. ^ Edge, Jake. "UEFI and "secure boot"". LWN.net. Retrieved 9 September 2012.
  56. ^ a b "Windows 8 Secure Boot: The Controversy Continues". PC World. Retrieved 9 September 2012.
  57. ^ "Secure Boot for ESXi 6.5 - Hypervisor Assurance". VMware vSphere Blog. 4 May 2017. Retrieved 18 August 2017.
  58. ^ HowTos/UEFI - CentOS Wiki
  59. ^ Larabel, Michael (30 April 2018). "Debian Making Progress on UEFI SecureBoot Support in 2018". Phoronix. Phoronix Media. Retrieved 23 May 2018.
  60. ^ Garrett, Matthew (27 December 2012). "Secure Boot distribution support". Mjg59.dreamwidth.org. Retrieved 20 March 2014.
  61. ^ "SecureBoot". FreeBSD Wiki. FreeBSD. Retrieved 16 June 2015.
  62. ^ a b "Unified Extensible Firmware Interface". UEFI Shell. Arch Linux. Retrieved 25 September 2013.[unreliable source?]
  63. ^ a b "EFI Shells and Scripting". Intel. Retrieved 25 September 2013.
  64. ^ a b "UEFI Shell Specification Version 2.0, Errata A" (PDF). Unified EFI, Inc. May 2012. Retrieved 25 September 2013.
  65. ^ "TianoCore on SourceForge". Intel. Archived from the original on 3 October 2013. Retrieved 25 September 2013.
  66. ^ "Email Archive: edk2-devel". [edk2] Inclusion of UEFI shell in Linux distro iso. SourceForge. 2012. Retrieved 25 September 2013.
  67. ^ "TianoCore on SourceForge". Shell FAQ. Intel. Retrieved 25 September 2013.
  68. ^ a b "Unified Extensible Firmware Interface". Launching UEFI Shell. Arch Linux. Retrieved 25 September 2013.[unreliable source?]
  69. ^ "Basic Instructions for Using EFI for Server Configuration on Intel® Server Boards and Intel® Server Systems" (PDF). Intel. 2008. Retrieved 25 September 2013.
  70. ^ "Unified Extensible Firmware Interface". bcfg. Arch Linux. Retrieved 25 September 2013.[unreliable source?]
  71. ^ "GRUB EFI Examples". Asus. Arch Linux. Retrieved 25 September 2013.[unreliable source?]
  72. ^ "TianoCore - coreboot". Retrieved 25 May 2012.
  73. ^ "SecureCore Tiano™". Phoenix Technologies. Archived from the original on 6 September 2010. Retrieved 14 September 2010.
  74. ^ "Aptio®: The Complete UEFI Product Solution" (PDF). American Megatrends, Inc. Retrieved 2 May 2018.
  75. ^ "Why US?". Insyde Software Corp. Retrieved 2 May 2018.
  76. ^ "Microsoft Announces "Project Mu" For Open-Source UEFI Alternative To TianoCore". Phoronix. Retrieved 20 December 2018.
  77. ^ "Marrying U-Boot UEFI and GRUB" (PDF). Retrieved 12 September 2018.
  78. ^ "UEFI on Top of U-Boot" (PDF). Retrieved 12 September 2018.
  79. ^ "Installing OpenBSD 6.3 on Raspberry 3". Retrieved 12 September 2018.
  80. ^ "iSCSI booting with U-Boot and iPXE". Retrieved 12 September 2018.
  81. ^ Apple Computer. "Universal Binary Programming Guidelines, Second Edition: Extensible Firmware Interface (EFI) Archived 24 July 2008 at the Wayback Machine"
  82. ^ Apple's Transition from Open Firmware to Extensible Firmware Interface, mactech, 2007.
  83. ^ a b "Intel® Platform Innovation Framework for UEFI Overview". Intel. Retrieved 14 September 2010.
  84. ^ Evaluating UEFI using Commercially Available Platforms and Solutions (PDF), UEFI, May 2011, archived from the original (PDF) on 22 March 2012
  85. ^ Asus P67 Motherboard Preview.
  86. ^ "Windows Hardware Certification Requirements for Client and Server Systems". Microsoft. January 2013. System.Fundamentals.Firmware.CS.UEFISecureBoot.ConnectedStandby ... Platforms shall be UEFI Class Three (see UEFI Industry Group, Evaluating UEFI using Commercially Available Platforms and Solutions, version 0.3, for a definition) with no Compatibility Support Module installed or installable. BIOS emulation and legacy PC/AT boot must be disabled.
  87. ^ "Microsoft: All You Need to Know About Windows 8 on ARM". PC Magazine. Retrieved 30 September 2013.
  88. ^ Richardson, Brian (30 October 2017). ""Last Mile" Barriers to Removing Legacy BIOS" (PDF). Retrieved 22 November 2017.
  89. ^ Announcement of release 3.5pre1 by maintainer Brett Johnson made on 27 February 2004.
  90. ^ EFI version of Grub, Debian GNU/Linux, retrieved 1 May 2008
  91. ^ a b c "Ubuntu will use GRUB 2 for its Secure Boot implementation". The H Online. Retrieved 28 October 2012.
  92. ^ OpenVMS Release History, HP, archived from the original on 5 January 2009, retrieved 16 September 2008
  93. ^ rEFIt — Windows Vista and EFI, SourceForge
  94. ^ "Extensible Firmware Interface", Windows Server TechCenter, Microsoft, archived from the original on 30 August 2006
  95. ^ "Unified Extended Firmware Interface support in Windows Vista". Microsoft. 26 October 2006. Retrieved 12 June 2010. Microsoft determined that vendors would not have any interest in producing native UEFI 32-bit firmware because of the current status of mainstream 64-bit computing and platform costs. Therefore, Microsoft originally did not to ship support for 32-bit UEFI implementations.
  96. ^ "Microsoft Touts Incredible Windows 8 Boot Times". Retrieved 9 September 2011.
  97. ^ Jon Brodkin (21 September 2011). "Windows 8 secure boot could complicate Linux installs". Ars Technica. Retrieved 23 September 2011.
  98. ^ "FreeBSD to get UEFI support". The H. Retrieved 7 March 2013.
  99. ^ "UEFI - FreeBSD Wiki". FreeBSD.org. Retrieved 19 June 2014.
  100. ^ "Oracle Solaris 11.1 — What's New" (PDF). oracle.com. Retrieved 4 November 2013.
  101. ^ "OpenBSD 5.9". www.openbsd.org. Retrieved 11 September 2016.
  102. ^ "OpenBSD 6.0". www.openbsd.org. Retrieved 11 September 2016.
  103. ^ Open Virtual Machine Firmware, SourceForge, archived from the original on 6 October 2011
  104. ^ "VMWare Workstation EFI firmware | VMware Communities". Communities.vmware.com. Retrieved 28 February 2014.
  105. ^ "Using EFI/UEFI firmware in a VMware Virtual Machine | VMware Communities". Communities.vmware.com. Retrieved 18 January 2016.
  106. ^ "Announcing VMware Workstation 14 - VMware Workstation Zealot". VMware Workstation Zealot. 22 August 2017. Retrieved 2 August 2018.
  107. ^ "What's New in vSphere 5.0". Vmware.com. Retrieved 28 February 2014.
  108. ^ "VMware vSphere 6.5 Release Notes". pubs.vmware.com. Retrieved 13 January 2017.
  109. ^ 3.1 Changelog, VirtualBox, archived from the original on 28 September 2010
  110. ^ Ticket 7702, VirtualBox
  111. ^ "Statement by sr. software engineer at Oracle", Forum, VirtualBox
  112. ^ "Testing secureboot with KVM". FedoraProject. Retrieved 28 February 2014.
  113. ^ "What's New in Hyper-V for Windows Server 2012 R2". MicrosoftTechNet. Retrieved 24 June 2013.
  114. ^ "Shielded VMs". Retrieved 16 February 2019.
  115. ^ "TianoCore on SourceForge: EDK2 Application Development Kit (EADK)". Intel. Retrieved 25 September 2013.
  116. ^ "Interview: Ronald G Minnich". Fosdem. 6 February 2007. Retrieved 14 September 2010.
  117. ^ Doctorow, Cory (27 December 2011), The Coming War on General Purpose Computation, retrieved 25 September 2013
  118. ^ "coreboot (aka LinuxBIOS): The Free/Open-Source x86 Firmware". YouTube. 31 October 2008. Retrieved 14 September 2010.
  119. ^ "Welcome", TianoCore, SourceForge, archived from the original on 23 April 2012
  120. ^ a b "Is Microsoft Blocking Linux Booting on ARM Hardware?". Computerworld UK. Retrieved 6 March 2012.
  121. ^ "Windows 10 to make the Secure Boot alt-OS lock out a reality". Ars Technica. Retrieved 21 March 2015.
  122. ^ "Shimming your way to Linux on Windows 8 PCs". ZDNet. Retrieved 26 February 2013.
  123. ^ a b "Ubuntu details its UEFI secure boot plans". Linux Weekly News. Retrieved 11 September 2012.
  124. ^ a b "No Microsoft certificate support in Linux kernel says Torvalds". The H. Retrieved 26 February 2013.
  125. ^ "Linus Torvalds: I will not change Linux to "deep-throat Microsoft"". Ars Technica. Retrieved 26 February 2013.
  126. ^ "Exclusive: Open software group files complaint against Microsoft to EU". Reuters. 26 March 2013. Retrieved 26 March 2013.
  127. ^ "Researchers demo exploits that bypass Windows 8 Secure Boot". IT World. Retrieved 5 August 2013.
  128. ^ MENDELSOHN, Tom (12 August 2016). "Secure Boot snafu: Microsoft leaks backdoor key, firmware flung wide open [Updated]". Ars Technica. Retrieved 12 August 2016.
  129. ^ a b "Linux on Windows 8 PCs: Some progress, but still a nuisance". ZDNet. Retrieved 26 February 2013.
  130. ^ "Lenovo UEFI Only Wants To Boot Windows, RHEL". Phoronix. Retrieved 26 February 2013.
  131. ^ "Linux acquitted in Samsung laptop UEFI deaths". Bit-tech. Retrieved 26 February 2013.
  132. ^ "Booting Linux using UEFI can brick Samsung laptops". The H. Retrieved 26 February 2013.

Further reading

Wikimedia Commons has media related to Extensible Firmware Interface.
Retrieved from "https://en.wikipedia.org/w/index.php?title=UEFI&oldid=944416302"