Announcing coreboot 4.1
coreboot.org
coreboot.org
It's a great project from user's perspective: healthy community, very interesting, quick-reward project to play with.
If you have a spare compatible thinkpad, I highly encourage you to try it out. :-) IIRC, there is a patch from me in coreboot -- it was so easy to prepare and submit one.
I'm reading the page at
http://www.coreboot.org/Board:lenovo/x60/Installation
and wondering how hard it would be to put coreboot on this. I'm also wondering about suspend, the BIOS settings (ability to switch a core off and change power profiles &c). It would also be really cool to have a QR code display when the laptop boots.
Have you done a write-up anywhere?
Since you're using gNewSense, you may appreciate what libreboot is doing with coreboot (libreboot:coreboot ~ kernel-libre:kernel)
For example the new Thinkpads (and other laptops/desktops) with the Broadwell U/Y series have "Intel Boot Guard" which cryptographically prevents a replacement BIOS from being flashed onto the hardware [1] I truly wonder what is the long term strategic benefit from doing this ? Isnt the only way to compete against Apple is to open up more ?
[1] http://www.coreboot.org/pipermail/coreboot/2015-February/079...
IMO the solution is economic. If a PC vendor wanted to ship Coreboot I'm sure they would find a way to do it. But people buying Windows PCs and installing Linux are keeping the "native" Linux PC market unsustainably small.
[1] http://blog.trendmicro.com/trendlabs-security-intelligence/h...
I'm trying to understand if there is an attack vector that is prevented by not allowing coreboot.
[1] http://www.theregister.co.uk/2015/07/08/microsoft_donates_to...
In theory, it should be possible to support user flashing of unsigned firmware, perhaps in some sort of OS-less boot mode that malware couldn't use. But offering that capability without it being a backdoor is costly and effortful enough that I don't really blame motherboard manufacturers for declining to do so on behalf of a rather niche use case.
It does increase security, since for instance in spite of its complexity Secure Boot has proven to be reasonably secure, and thus it is simpler to attack the firmware.
However I agree with Garrett and disagree with aaronem: just as shown by Secure Boot on x86, you can have a reasonable choice between security and user's choice i.e. you can give freedom and security. A similar mechanism, in which a user could enroll its keys and install its signed coreboot payload, is possible. The same applies to TPM. Given that Intel had 55 bilions in revenues last year, I see no reason to cut them any slack (same goes for Apple, Qualcomm, etc).
As far as the "new Microsoft" goes, the policy on Windows phone is the same on Windows 10 as it was on Windows RT and Windows 8: Secure Boot on ARM is locked down in such a way that the user cannot add its own keys, or send a binary to Microsoft to have its signed for 99$ (i.e. the result is functionally equivalent to Apple policy with ios). If you sell devices on which the users can't even decide which kernel to boot, you probably don't have a problem with devices in which the users can't decide which firmware to use.
They even provide 'libpayload' for building your own boot payloads. Totally awesome.
Now only if I could get Supermicro servers with coreboot by default, or some similar bare bones value brand...
http://store.netgate.com/ADI.aspx https://github.com/ADIEngineering
I have NO affiliation with these companies. I'm simply happy that they are shipping Coreboot.
What's the cheapest non-QEMU way to play with coreboot?
Also Gluglug, that builds 100% free (as in freedom) laptops - http://shop.gluglug.org.uk/
https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-... http://www.coreboot.org/Board:lenovo/x201
alternatively, do post in /r/thinkpad
Feel free to contact me if you have any questions about BITS. (Or if you have fun playing with it.) It's a lot of fun to work on, and it's a lot of fun to talk with people who use it.
> What's the cheapest non-QEMU way to play with coreboot?
A Chromebook. You can replace the read-write BIOS safely, as the system is always completely recoverable via the read-only BIOS. If you want to be able to replace the read-only BIOS as well (by turning the write-protect screw), get a Servo debug board, and read the online instructions for adding a Servo debug port to your Chromebook board. (Those boards typically have the debug header, just not the connector.)