4 ms·
I applaud moving away from UEFI, to something simpler and more transparent, and something not hostile from the start to open source. I like how relatively simp
by neilv 7y ago
I applaud moving away from UEFI, to something simpler and more transparent, and something not hostile from the start to open source.
I like how relatively simple my Coreboot systems are. The sooner that Coreboot can minimally initialize hardware and invoke an open source bootloader or Linux kernel payload directly, the better. (Bonus, if the kernel doesn't need legacy PC BIOS services.)
Regarding concerns raised in the article, I'd be more suspicious of closed microcode and firmware blob parts, than of open source parts. Many knowledgeable eyes on the open parts can help. Though, of course, open parts could, in theory, be crafted to provide affordances for naughtiness involving closed parts. I have mixed feelings about recent initiatives to push closed updates more widely and reliably, and look forward to more-open hardware.
- maze-le 7y ago>> Many knowledgeable eyes on the open parts can help Well, that is the problem. No one (well, say very very few) do code reviews on their own -- they do not provide as much benefits as coding (learning and reputation wise). Its a bit like the problem in academic publishing: Replication trials are not prestigious enough, so they are done far to rarely, albeit they are very important. There are companies out there, that will do it for money, and many great open source products have been reviewed that way. But I don't think this happens often enough.
- PakG1 7y agoWhile that's a valid concern, the real question should be: despite that, is it more trustworthy than closed source or not?
- maxheadroom 7y ago>...they do not provide as much benefits as coding (learning and reputation wise). I think that's because code reviews have changed from being helpful form of preventing you from stubbing yourself on your toe to, "Why would you do this...? No0b..." kind of format. If code reviews were weighted as equally beneficial to the code and as being approached as being beneficial to the growth of the developer making the change, then I could see it having much more benefit in learning; however, that would take a dynamic change in the general culture. ...but saying that code reviews don't provide as much learning benefit is to just infer that there's nothing that can be done about that when, in fact, there is. :)
- tomatocracy 7y agoI suspect that code openly contributed by the NSA will get quite a lot of scrutiny - more than average code contributions. For that reason, if they wanted to subvert something like this, I doubt they'd advertise the source of the contributions like this.
- stjohnswarts 7y agoLOTS of security companies do code reviews and constantly looking for security holes in OSS, it is after all a huge feather in their cap and reputation boost to find holes and earn the big $$. Imagine if they were able to find a deliberate hole in NSA provided UEFI code.
- JohnStrangeII 7y agoI still think it's problematic, since it is in the vital interest of the NSA, and one of its core missions, to be able to penetrate endpoint security at that level. If they contribute to Coreboot, then that means either that they want to compromise the project or that their "tailored access" group already has enough other ways of comfortably breaking the security of any PC at a level that is low enough (to evade all user-level software, anti-virus vendors, etc.). Both possibilities are bad for international users, even if the second one is obviously more preferable. It makes no sense for the NSA to assist making PCs secure for non-military use and for use by non-US citizens against their own attacks, because it contradicts their mission statements. The only other (not totally implausible) explanation is that different departments within the NSA are so disconnected from each other that they have started to work against each other.
- cm2187 7y agoYou can’t really avoid it anyway. How do you know a contributor isn’t secretly working for the NSA (or a foreign equivalent). The only way to prevent backdoors is to inspect the code and keep it small and simple.
- chongli 7y agovital interest of the NSA, and one of its core missions, to be able to penetrate endpoint security It's also a core mission of the NSA to protect US networks from attack. If they're inserting backdoors in products used by US businesses, they're directly undermining their core mission.
- oefrha 7y ago> If they're inserting backdoors in products used by US businesses, they're directly undermining their core mission. Which is not unheard of.
- petre 7y agoYou mean like the NIST ECC curves backdoored by the NSA? https://www.miracl.com/press/backdoors-in-nist-elliptic-curves https://www.miracl.com/press/backdoors-in-nist-elliptic-curv...
- Conan_Kudo 7y ago> I applaud moving away from UEFI, to something simpler and more transparent, and something not hostile from the start to open source. Coreboot is not an alternative to UEFI. You can make TianoCore builds that use Coreboot, even!