News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by hendzen on Tuesday February 16, 2016 @09:57AM (#11110182)
So are you personally volunteering to rewrite all of Linux and glibc in Rust? Are you or your employer volunteering to fund such efforts? There is a reason it hasn't happened yet - because doing so would be exceptionally time consuming and expensive.
Re:Glibc getaddrinfo stack-based buffer overflow by efuquen on Tuesday February 16, 2016 @10:06AM (#11110249)
I think OP isn't naively assuming it would be easy, or any one person would do it. More the point is there probably isn't enough of an effort or emphasis on the Linux/OSS communities part to even attempt it.
Re:Glibc getaddrinfo stack-based buffer overflow by golergka on Tuesday February 16, 2016 @10:16AM (#11110326)
Right now, companies that run linux on their servers don't have to pay huge fines when security meltdowns happen.

I imagine if they would, they would put more money into the problem: either fund linux development or created more of a market for commercial server operating systems (which can still be open source, at least in some interpretations of the term), for example.

Re:Glibc getaddrinfo stack-based buffer overflow by nitrogen on Tuesday February 16, 2016 @12:36PM (#11111576)
No. Strict liability for third party software failure is not a good idea. Software gains much much more from the freedom to innovate than it loses from exploits. Strict liability would be a terrible blow against basically everything HN represents.
Re:Glibc getaddrinfo stack-based buffer overflow by golergka on Tuesday February 16, 2016 @12:51PM (#11111724)
Well, there are areas where freedom to innovate is more important, and then there are areas where liability is more important.

May be US (as de-facto main government-level actor in IT and internet) could create voluntary certification that opened up companies to such liabilities? Small startup operating from a garage — no certification necessary, but users are aware that no one is guaranteeing anything. IBM? Level A certification which they advertise everywhere, with billions of dollars in potential fines.

Re:Glibc getaddrinfo stack-based buffer overflow by ivl on Tuesday February 16, 2016 @01:01PM (#11111789)
If it was voluntary, I doubt many of those companies would see it as worth the risk. The problem is that these errors happen because so many people are working on interdependent parts. Many times, it's not even your error that can make your software vulnerable. I dislike making anything so risky, because we'll see much, much less good software at the end of the day.
Re:Glibc getaddrinfo stack-based buffer overflow by ptaipale on Wednesday February 17, 2016 @04:13AM (#11116438)
Plus a culture of risk-avoidance, blame-shifting and bureaucracy-over-innovation.

I even feel the breath of having Ada (the language) enforced over all of us again, and similar ideas...

(Not that Ada is so bad as a language, it's more about the ideas of enforcement and top-down control...)