3 ms·
Do we call it sophisticated to cover up how embarrassing it was and the fact that it lurked in what is an obvious attack vector in retrospect? It just shined a
by kortilla 6y ago
Do we call it sophisticated to cover up how embarrassing it was and the fact that it lurked in what is an obvious attack vector in retrospect?
It just shined a light on how shaky the foundation is we’re standing on. This is relatively tame considering its just some back-doored bolt on software.
What happens when it’s the build compiler for the Windows OS? How about the intel NIC firmware?
Our only answer seems to be even more automated updates. Yet that means a slip up in chrome build security could compromise tens of millions of people in a week.
It’s mind boggling how fragile all of this is. It’s barely safe with insiders behaving correctly.
How many people do you think have to sign off on a code change driving the Qualcomm chipset in your phone? My guess is 1, and that’s if it’s a “modern” development process. So that’s it, two people colluding and you’ve got a back door worth a fortune to a nation state.
What a fucking mess.
- KirillPanov 6y ago> Our only answer seems to be even more automated updates No, exactly the opposite. Automatic updates are insane. If software updates itself automatically, you need to assume it is compromised. If software requires manual updates, you need to assume that the more frequent the updates, the less secure it is.