4 ms·
Critical systems should be open source by law.
by swiley 11y ago
Critical systems should be open source by law.
- brohee 11y agoNot sure it would help any, it's not exactly hard to find very low quality code on Github. It IMHO shows a failure of the type approval process, maybe it didn't evolve enough with regard to the amount of software used in safety critical components. Inspiration from aircraft certification would likely be mùore than welcome in that regard...
- PakG1 11y agoThe point is that a world of coders who would be mulling over the code due to interest and spare time would likely find critical issues and shine light onto them, making it a PR issue for those companies. If those companies ever get around to offering bounties for issues relating to safety or security, even easier to get an army of eyes on the code.
- TeMPOraL 11y agoThat's the point. We already know it doesn't work. Most recent examples would be Heartbleed, ShellShock, etc.
- Lewton 11y agoOSS having bugs is not proof that open sourcing software won't lead to less bugs.
- TeMPOraL 11y agoI'm only trying to show that you can't shout "Open Source!" and get magical immunity from bugs in life-critical software. We need to think of something else instead, or in addition to, open-sourcing to meaningfully reduce the amount of those bugs.
- Jemmeh 11y agoI agree. The main component of safety and security--is making it part of the software development process itself. Nothing can substitute for that, and it's what the article is addressing. Open source would be "nice", but it's just the training wheels, while safety and security baked into the process is the front tire. Might help it from not falling over but you're not going anywhere in the right direction without the right foundation.
- snowwrestler 11y agoHeartbleed and ShellShock are examples of why open source is better. Both were found by folks who were not the software maintainers, but were reviewing the source code independently. In comparison, it took multiple deaths and a major lawsuit to create the same level of visibility into Toyota's codebase. And what reviewers found was code quality far worse than that of OpenSSL or bash. Someone else said this in another HN thread, but I love it: imagine a world in which Consumer Reports car reviews include a code audit report. That would be far, far better for overall safety than the current situation.
- TeMPOraL 11y agoI agree. I might have stated my point too strongly. I just think that going Open Source won't magically fix things. ShellShock and Heartbleed were out there for many years before someone reported on them, with (AFAIR) evidence of those holes being exploited by malicious actors. Trying to force a switch to Open Source won't improve situation very much, while requiring a serious overhaul of how the entire world does business. It doesn't seem to be worth it without introducing additional ways to fix the software creation and testing process.
- fahadkhan 11y ago"spare time", do you know where I can find some of that?
- a3n 11y ago> Not sure it would help any, it's not exactly hard to find very low quality code on Github. Because it's open and findable. I think that was the point.
- hoorayimhelping 11y agoI love magic bullets! As we've recently seen with things like Heartbleed, open source has no vulnerabilities, no bugs, no errors, and is free from all the problems of proprietary software.
- eru 11y agoSee https://en.wikipedia.org/wiki/Heartbleed#Discovery https://en.wikipedia.org/wiki/Heartbleed#Discovery It looks like at least having the source available made it easier for the good guys to discover the bug.
- Jtsummers 11y agoOne of the problems with embedded systems like this is that very few eyes ever see the code. Even in more regulated fields like avionics. The code will be examined primarily by the developers, testers, their QA and maybe the company that hired them if it's contracted out. Instead, what gets examined are the artifacts like requirements documents, the results of tests, specifications and such. This allows poor code quality to be hidden, and, to some extent, encourages sloppy development practices (especially when time is critical). Exposing the code to more people will have several effects, but the main two (from my perspective) are: * Developers won't release as much bad code, either due to pride or insistence from their management. * Bugs may be more easily discovered and diagnosed if the code is available. As it is now, it's a black box. So if I find an issue I may be able to repeat it, but I can't examine the code to see why it's actually happening or to correct it.
- nkrisc 11y agoAnd then it was discovered and fixed.
- snowwrestler 11y agoHeartbleed is the perfect example of why critical code should be open source. It was discovered by developers who were not the original coders, and they were able to talk about it freely, essentially marketing it to create awareness. If OpenSSL was closed-source my servers would probably still be vulnerable today.