3 ms·
> As soon as you patch software, it's now in an unpatched state relative to the next patch/product update which is a certain event. Why do you bother taking sh
by josephcsible 4y ago
> As soon as you patch software, it's now in an unpatched state relative to the next patch/product update which is a certain event.
Why do you bother taking showers? You're just going to start getting dirty again as soon as you get out.
> But the difference between a modern system patched only a few months ago or last year and "today" is only a bunch of unlikely exploitable edge cases, and a whole lot of product update gunk.
> Typical patch notes: "possible code injection when unlikely event A happens at the same time as unlikely event B.".
This isn't true. A lot of new vulnerabilities are easily exploitable.
- exodust 4y ago> Why do you bother taking showers? Because our bodies accumulate and generate dirt over time which needs washing off. Software doesn't accumulate dirt or generate problems over time, so your analogy doesn't fit. > This isn't true. We are not playing "who knows the truth", we're having a discussion. What I said is not false. The vast majority of typical patch notes detail vulnerabilities which can happen only when certain variables align. "Easily exploitable" may be true, provided certain other unlikely conditions are met, such as the attacker already gaining access to your system in order to exploit said vulnerability. This is not a "seat belts" vs "no seat belts" risk. I maintain that the risk from not embracing whatever tech giant's update ideology is commanded, is overstated most of the time compared to other risks people face online.
- josephcsible 4y ago> Software doesn't [...] generate problems over time But that's exactly what happens when new vulnerabilities are found.