2 ms·
I think this is very good because it reduces the attack surface for people who track current code. It's important to remember a large set of un-updated nodes w
by ggm 8y ago
I think this is very good because it reduces the attack surface for people who track current code.
It's important to remember a large set of un-updated nodes will remain. Not that anyone can do much, but equally not that the entire surface of bad Wordpress will go away. I would be interested how big the long tail is. one third? more?
It is also worth thinking about the code signing problem firefox just had, and reflecting on the possibility of the hack in the head still taking place: either a denial-of-service or a bad code intrusion risk remains.
Its far far less likely, and it can be mitigated, but this is the reality of distributed systems: You can only do the best you can, nothing is guaranteed. (even TMR units fail)