3 ms·
https://news.ycombinator.com/item?id=41006104#41006555 https://news.ycombinator.com/item?id=41006104#41006555 the flawed data was added in a post-processing st
by password4321 2y ago
https://news.ycombinator.com/item?id=41006104#41006555 https://news.ycombinator.com/item?id=41006104#41006555
the flawed data was added in a post-processing step of the configuration update, which is after it's been tested internally but before it's copied to their update servers
per a new/green account
- cududa 2y agoSo have we decided to stop using checksums or something?
- password4321 2y agoPerhaps it was the checksum/signature process!
- function_seven 2y agoYa gotta keep checksumming until you find a fixed point.
- spaceywilly 2y ago“And so that’s why we recommend using phased rollouts” -Every DevOps engineer from now on
- prox 2y ago“But that costs us money and time” - some suit.
- Woodi 2y ago"And they promise fast threat mitigation... Let allow them to take over EVERYTHING! With remote access, of course. Some form of overwatch of what they in/out by our staff ? Meh... And it even allow us to do cuts in headcount and infra by $<digits_here> a year."
- mihaaly 2y agowhen something is changed, we usually re-test. that's the whole point of testing anyway. :)