Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

https://hackertimes.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



“And so that’s why we recommend using phased rollouts” -Every DevOps engineer from now on


“But that costs us money and time” - some suit.


"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."


So have we decided to stop using checksums or something?


Perhaps it was the checksum/signature process!


Ya gotta keep checksumming until you find a fixed point.


when something is changed, we usually re-test. that's the whole point of testing anyway. :)




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: