←back to thread

28 points todsacerdoti | 2 comments | | HN request time: 0.388s | source
Show context
KellyCriterion ◴[] No.46252778[source]
industry-proven and mature libs like LOG4J or LOG4Net are not sufficient?
replies(4): >>46254636 #>>46306388 #>>46306464 #>>46306602 #
hansvm ◴[] No.46254636[source]
You mean this log4j [0] with major vulnerabilities the industry missed for nearly a decade?

[0] https://en.wikipedia.org/wiki/Log4Shell

replies(3): >>46254979 #>>46255024 #>>46306127 #
1. mashepp ◴[] No.46254979[source]
So you don’t use any software that has had a security vulnerability?

What operating system and browser did you use to write your post?

replies(1): >>46306082 #
2. Veserv ◴[] No.46306082[source]
Unary thinking has no place when considering software quality or security. Just because things have vulnerabilities does not mean that the category, severity, and frequency of them is a irrelevant consideration.

The Log4j vulnerability was effectively calling eval() on user input strings. That is utter incompetence to the extreme with immediately obvious, catastrophic consequences to anybody with any knowledge whatsoever of software security. That should be immediately disqualifying like a construction company delivering a house without a roof. "Oh yeah, anybody could forget to put a roof on a house. We can not hold them responsible for every little mistake." is nonsense. Basic, egregious errors are disqualifying.

Now, it could be the case that everything is horribly defective and inadequate and everybody is grossly incompetent. That does not somehow magically make inadequacy adequate and appropriate for use. It is just that in software people get away with using systems unfit for purpose because they had "no choice but to use substandard components and harm their users so they could make money".