News for hackers. Stuff that matters.
Re:Twitter has and internal root CA problem by ilyt on Monday March 13, 2023 @07:07AM (#35134016)
We have 7 racks and 3 people working in ops and built Puppet setup "right". It's not hard. And their setup was probably right too.

Just that nobody plans for "bus hit our entire ops team"

Re:Twitter has and internal root CA problem by jojobas on Monday March 13, 2023 @07:18AM (#35134115)
More commonly you don't plan for it, you make sure the entire ops team are never on the same bus, same plane, preferably not even in the same city.
Re:Twitter has and internal root CA problem by hef19898 on Monday March 13, 2023 @08:10AM (#35134580)
All fine and good. Until the new owner just fires everyone over night anyway. At which point, I guess, it is not the previous ops team's problem anymore.
Re:Twitter has and internal root CA problem by VoidWhisperer on Monday March 13, 2023 @09:45AM (#35135647)
Unfortunately even those precautions wouldn't save you from the 'holy shit basicially the entire ops team got fired out of nowhere' scenario..
Re:Twitter has and internal root CA problem by rsynnott on Monday March 13, 2023 @01:58PM (#35139712)
_Nothing_ can save a company from sufficiently incompetent future management, ultimately.