5 ms·
UEFI on top of U-Boot on ARM
- mariuolo 10y agoDoes this also come with an increase in surface attack from malware?
- josteink 10y agoDon't believe the FUD. UEFI does not increase attack surface. It reduces it through means such as secure boot. The other option is insecure booting with no verification, and if your malware is running with privileges to be able to inject itself into the boot process, the machine is already compromised anyway. In this case secure boot provides some means of protection. People not using UEFI however, they are vulnerable and most likely affected.
- amluto 10y agoI would argue that, taking Secure Boot as a given, the UEFI design provides an amazingly large surface which to attack Secure Boot.
- josteink 10y agoUnless you're arguing for something new and different, the only other option you have to UEFI secure boot, is completely unverified boot which provides zero security. And that has to be less secure than UEFI by definition. In that regard arguing about how UEFI brings attack surface seems misguided. Yes, there's is an attack surface, but that's only because now there is something to attack where there previously was a fully open door. What you're saying is pretty much that any imperfect security measure lessons security compared to no measure at all, because it brings attack surface. That's a fairly backwards way of thinking.
- mappu 10y agoPatch from February - how far is this along?
- nwmcsween 10y agoWhy not barebox[1] which iirc is a fork of U-boot that does EFI, etc? [1]http://www.barebox.org/ http://www.barebox.org/
- wkz 10y agoAs someone who has added support for a few boards to both U-Boot and Barebox, I really recommend looking at Barebox first. U-Boot does have support for more architectures and SoCs, but the Barebox code base is of _much_ higher quality. Also, the bourne-like shell is a pleasure to work with!
- Quequau 10y agoUEFI is one of the blocking hurdles for running CoreOS on Raspberry Pi and ODROID boards. I wonder if this would help overcome that.
- voltagex_ 10y agoTaking a different approach is EFIDroid - http://efidroid.org/ http://efidroid.org/
- userbinator 10y agoI know there is no real standard for ARM booting, but would it really have been too hard to come up with something simpler and more like what PC BIOS does? Then again, if you're already choosing to use grub, I guess you probably don't care... When enabled, the resulting U-Boot binary only grows by ~10kb, so it's very light weight. For comparison, the original PC BIOS, which includes far more functionality than just a bootloader, is 8KB.
- rwmj 10y agoFor aarch64, SBBR http://infocenter.arm.com/help/topic/com.arm.doc.den0044b/DEN0044B_Server_Base_Boot_Requirements.pdf http://infocenter.arm.com/help/topic/com.arm.doc.den0044b/DE... If you were expecting it to be lightweight, I'm afraid I've got disappointing news for you. The UEFI/aarch64 binary is 2MB or so. But it's like a mini-operating system with drivers for a bunch of disk hardware, network devices and filesystems, because it supports network booting and booting from files located on local disks (so similar to grub).
- dTal 10y agoMini??? I seem to recall you used to be able fit Linux on a 1.44 megabyte floppy...
- rwmj 10y agoProbably not a version of Linux that can drive multiple types of recent PCIe graphics adapter, USB, SCSI hostadapter and network card though. While I have no great love for UEFI, it's damn convenient to be able to use the UEFI command line to mount up local filesystems, browse files etc when troubleshooting boot problems. Also to be able to plug in a USB key, see the files there, and try booting from one of them. Since SBSA/SBBR is used almost exclusively on servers, 2 MB - so what?
- chme 10y ago> While I have no great love for UEFI, it's damn convenient to be able to use the UEFI command line to mount up local filesystems, browse files etc when troubleshooting boot problems. Also to be able to plug in a USB key, see the files there, and try booting from one of them. So UEFI can to the same as a much smaller u-boot?
- green7ea 10y agoWhy not coreboot?
- mixedCase 10y agoGotta NIH fast.
- green7ea 10y agoCould you please explain what NIH is.
- craigcabrey 10y agoNot invented here syndrome.
- syntheticnature 10y agoGiven it looks like coreboot's ARM support is still not quite there from what I can see, I'm not surprised they picked u-boot which has been running on ARM for some time.
- brynet 10y agoThis is the method that OpenBSD will be using for the armv7 port starting with 6.0, a version of u-boot loader loads our EFI bootloader ported to ARM, along with .dtb/FDT (Flattened Device Trees) files for each system that is currently supported. http://www.openbsd.org/60.html http://www.openbsd.org/60.html It's actually pretty cool, the advantages of this approach are: * We can use our standard boot(8) loader, which has already been ported to EFI for i386/amd64. Code sharing! :-) * There is a single ELF kernel for all supported SoCs, no longer need special u-Boot headers/images. * The kernel can be loaded off of our native filesystem (FFS/UFS) vs. FAT/ext2. The kernel can live inside the root filesystem and be updated normally.