EFI and Linux: the future is here, and it's awful - Matthew Garrett

Channel:Linux.conf.au 2012 -- Ballarat, Australia · Length:53:10 · Published:2012-01-20 · Views:76975

Watch on YouTube

Summary

Matthew Garrett's linux.conf.au 2012 talk covers EFI and UEFI from the Linux point of view: why the PC BIOS was bad, what EFI changes, the issues it brings, and Secure Boot.

Why HN recommends it

Pointed to as an entertaining, informative explanation of why UEFI is troublesome, from a Linux UEFI developer.

A thoroughly entertaining and informative talk on issues including secure boot, but also other issues with UEFI. — HN, 2012

Operating systems & kernels · Linux & open-source ecosystems · Security & hacking

Subtitles (excerpt)

Garrett here uh a colel developer at Red Hat uh specializing in power management um and firmware development um we are discussing today um uh EFI and Linux the future is here and it is awful uh I have been told that his opinions on firmware quality are mostly unprintable but I have seen some of them printed in the past um on behalf of uh Linux con Au 2012 and bat um I hope we can we give you a very warm welcome Matthew gett hi so as you said my name is Matthew Garrett I work for Red Hats I used to focus mostly on power management suspend resume on laptops acpi and stuff more recently I've been working on UEFI which uh I'll introduce in a bit more detail main reason that I ends up working on ufi is that nobody else was and I'm really really bad at realizing that when there's nobody working on something there's probably a reason for that so anyway as you may have go gathered from the talk presentation and my title uh talk title in my introduction slides I'm not necessarily a huge fan of certain aspects of UEFI but we'll we'll get to that firstly we should talk about what EFI is now you buy a PC at the moment well for the past 20 years if you've bought a PC when you turn it on it executes some code in ROM or in Flash that is called the BIOS basic input

On Hacker News

EFI even talks FAT and there exists licensing such that you can use FAT for EFI reasons without any patent worries. I'm not saying that's a bad decision, just pointing out it is another thing that happened. I heard that fact in a linux.conf.au talk by the guy what did UEFI work for linux [0]. If you're sad to hear about the Microsoft influence, dude isn't too hot on the implementation of this new… — forgottenpass, 2013-11
Matthew gave an awesome talk on UEFI at linux.conf.au 2012 [0]. A thoroughly entertaining and informative talk on issues including secure boot, but also other issues with UEFI. It even got voted one of the best four talks at the conference, so he did the talk again at the end of the conference. This was great because I missed it the first time. My favourite quote from the talk was: "Files contain… — pserwylo, 2012-11
You can get around UEFI Secure Boot by installing an old signed bootloader with known exploits (if I understand correctly this is why the "Secure Golden Key Boot" exploit of last year[1] cannot be patched without changing public keys in the UEFI firmware). Not only that, the code that is shared by most UEFI implementations is garbage[2] with a large attack surface; exploits against the firmware i… — sedachv, 2017-07
Yeah, Matthew Garrett also gave a pretty detailed talk about it Linux.conf.au 2012, which reaches a similar conclusion: [VIDEO] — dlitz, 2016-08
Sorry, but the BIOS had many issues, and UEFI provided a solution to them, even if it wasn't an inherently good system. 1.The BIOS isn't portable, you can compile UEFI for any platform by porting a small base module. Everything uses this module, so the compiler will take care of the rest. 2. BIOS was a heap of 16bit assembly code, with a small memory space. It was quite hard to add any kind of co… — keeperofdakeys, 2013-01

Related videos