News for hackers. Stuff that matters.
Re:Twitter has and internal root CA problem by DrScientist on Monday March 13, 2023 @06:30AM (#35133711)
If this is true - who knows - then it reflects rather badly on the people who were fired - as they didn't implement safeguard for a 'run over by a bus' scenario when they were in charge.
Re:Twitter has and internal root CA problem by zer0tonin on Monday March 13, 2023 @06:31AM (#35133717)
There's "run over by a bus" and "90% of the company got ran over by a bus" scenarios. The second one is rarely worth implementing.
Re:Twitter has and internal root CA problem by walrus01 on Monday March 13, 2023 @06:35AM (#35133757)
There's also possibility of: "If this person hadn't been fired, they could use some other form of credentials within twitter's internal systems plus a passphrase they have memorized to login to the private-key-repository system where the credentials for the root CA are stored and retrieve them. But as they were fired abruptly they are not inclined to help Musk. And nobody has asked them".
Re:Twitter has and internal root CA problem by concordDance on Monday March 13, 2023 @07:22AM (#35134149)
Arent abrupt firings the norm in the USA?

My company had layoffs last year and the US people were gone the same day.

Re:Twitter has and internal root CA problem by PeterisP on Monday March 13, 2023 @07:55AM (#35134429)
Sure, but you do abrupt firings of whole teams only if you don't need what these teams do.

It is quite reasonable if a company's response plan for scenario "what if we intentionally shoot ourselves in the head" is "don't do that, why would we do that?".

Re:Twitter has and internal root CA problem by dragonwriter on Monday March 13, 2023 @02:07PM (#35139863)
> Arent abrupt firings the norm in the USA?

Abrupt firings of everyone with critical access, primaries and backups, is not, because its suicide. (Also why critical access roles are vetted carefully, because you want to make sure there is a lower-than-normal chance you will need to fire any of them, since that’s how you minimize the chance of a situation where you’d want to fire enough of them to cause a critical situation.)

If you do need decide there’s a problem that requires you to fire those people, you find every way possible to delay firing some of them while you expand the set of people with that access (which may be only momentary, by compelling them to hand over credentials as part of the exit process, if you have confidence that you can do that successfully.)

Re:Twitter has and internal root CA problem by a2800276 on Monday March 13, 2023 @07:06AM (#35134008)
Not to forget the "90% get fired my an egotistical maniac who expressed his distain by quite publicly calling them lazy useless pieces of shit" scenario. That scenario is also seldom considered.
Re:Twitter has and internal root CA problem by fredoralive on Monday March 13, 2023 @06:34AM (#35133744)
Or they had a "run over by a bus" scenario that assumed that the entire team wasn't going to be run over by a bus all at the same time?
Re:Twitter has and internal root CA problem by tedivm on Monday March 13, 2023 @09:46AM (#35135648)
I've worked at companies where we've had policies about how much of the company can travel together (ie, how many people can be on the same plane). If your entire team is fired then the company is the problem, not the team.
Re:Twitter has and internal root CA problem by raizer88 on Monday March 13, 2023 @06:33AM (#35133740)
Maybe building it right cost 5x, and you have a budget for 1x. Sometime money is not unlimited even at FAANG
Re:Twitter has and internal root CA problem by DoctorOW on Monday March 13, 2023 @06:57AM (#35133943)
To add on, people forget that Twitter was never really FAANG. It not only wasn't profitable but had no monetization plan for years. I'm sure it paid off for all the investors who got Elon's money but even as a Facebook competitor they don't have Facebook money.
Re:Twitter has and internal root CA problem by ilyt on Monday March 13, 2023 @07:08AM (#35134026)
TWAANG wouldn't sound bad tho
Re:Twitter has and internal root CA problem by orwin on Monday March 13, 2023 @09:37AM (#35135539)
It was profitable in 2019 and 2020, and could have been in 2022 (the first semester was huge, probably because of all the stuff happening all over the world).
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.
Re:Twitter has and internal root CA problem by nindalf on Monday March 13, 2023 @06:57AM (#35133945)
It reflects rather badly on you that you're talking mad shit without knowing their circumstances. What's the bus factor on your systems? Can they handle literally every person being fired overnight?
Re:Twitter has and internal root CA problem by rsynnott on Monday March 13, 2023 @07:18AM (#35134112)
It's normal to plan for scenarios where you abruptly lose some people. It's... less normal to plan for scenarios where you abruptly lose basically everybody; in most cases where that happens the company is basically dead anyway, so they're arguably not worth planning for.
Re:Twitter has and internal root CA problem by delfinom on Monday March 13, 2023 @09:58AM (#35135776)
It's management job to plan for run over by a bus scenario, not the people whose job is to actually implement things.
Re:Twitter has and internal root CA problem by dragonwriter on Monday March 13, 2023 @02:09PM (#35139892)
There’s “someone got run over by a bus outside of our control” and “The people in charge direct a bus to run over everyone covering a key function”. You don’t really plan for the latter scenario when you are in charge, instead, you just don’t direct a bus to do that. If your successor decides to do that, that’s…on them.