News for hackers. Stuff that matters.
Re:All extensions disabled due to expiration of intermediate... by driverdan on Friday May 03, 2019 @10:04PM (#19823850)
First they force code signing on everyone without a way to disable it then they break it. This is an extreme level of incompetence I didn't expect from Mozilla.

They'd better have the best post mortum ever, possibly with someone being fired.

Re:All extensions disabled due to expiration of intermediate... by weavejester on Friday May 03, 2019 @10:54PM (#19824074)
A mistake of this magnitude cannot be the fault of an individual, because if it was, then the organization lacked adequate safeguards.

What I'd like to see is a post-mortem, followed by an explanation of how they'll prevent the mistake from being made again in future.

Re:All extensions disabled due to expiration of intermediate... by tomschlick on Saturday May 04, 2019 @01:20AM (#19824617)
> how they'll prevent the mistake from being made again in future

This could have been prevented by someone putting the expiration date on the team shared calendar with a 60 day alert.

Re:All extensions disabled due to expiration of intermediate... by driverdan on Friday May 03, 2019 @11:07PM (#19824138)
I hope you're correct.
Re:All extensions disabled due to expiration of intermediate... by cjbprime on Friday May 03, 2019 @10:05PM (#19823853)
> They'd better have the best post mortum ever, possibly with someone being fired.

Arguably these two goals are incompatible. :)

Re:All extensions disabled due to expiration of intermediate... by AnIdiotOnTheNet on Friday May 03, 2019 @10:10PM (#19823880)
People are generally not inclined to be truthful about their mistakes if they expect to be punished for them. Its how problems keep getting covered up until they become catastrophes.
Re:All extensions disabled due to expiration of intermediate... by dev_dull on Friday May 03, 2019 @11:05PM (#19824125)
I guess it depends on if it was an honest mistake or gross negligence. I don’t think people should be fired for mistakes. I also don’t think everyone should be trusted with important tasks.
Re:All extensions disabled due to expiration of intermediate... by naikrovek on Friday May 03, 2019 @10:35PM (#19823993)
Come on, people make mistakes. Things fall through cracks. Shit happens, etc.

No one needs to be fired for a single instance of a particular mistake. If this happened multiple times, then I would be on board with firing someone.

Re:All extensions disabled due to expiration of intermediate... by hu3 on Friday May 03, 2019 @11:51PM (#19824328)
Mistakes of this magnitude are always singular and particular. Hopefully.
Re:All extensions disabled due to expiration of intermediate... by steve19 on Friday May 03, 2019 @10:21PM (#19823924)
Why does someone need to be fired? Does some blood spilled really make it better? Have some compassion.
Re:All extensions disabled due to expiration of intermediate... by driverdan on Friday May 03, 2019 @10:33PM (#19823982)
I'm generally not a fan of firing people for making mistakes. This one is so monumental it may require it though. This breaks most FF installations.
Re:All extensions disabled due to expiration of intermediate... by steve19 on Friday May 03, 2019 @10:37PM (#19824003)
You didn't answer my question. What does firing achieve? You fire a person who learnt their lesson and will never make the mistake again? And then hire someone new?

Or you fire the scapegoat because of a broken system that allowed one person to make a mistake?

Re:All extensions disabled due to expiration of intermediate... by driverdan on Friday May 03, 2019 @11:06PM (#19824134)
If this mistake was due to incompetence then the person should be fired. Incompetence shouldn't be tolerated.

But we're outsiders looking in and don't know what's going on at this point. That's why I used the qualifier "possibly." It's quite possibly it wasn't incompetence.

Re:All extensions disabled due to expiration of intermediate... by floatingatoll on Saturday May 04, 2019 @01:35AM (#19824661)
“quite possible”
Re:All extensions disabled due to expiration of intermediate... by luckylion on Saturday May 04, 2019 @12:41AM (#19824498)
> You fire a person who learnt their lesson and will never make the mistake again?

That's true, sort of. How often do you let people make huge mistakes before you decide that maybe they are just not apt for the position that they've been promoted to and Peter was right? Once? Twice? And unlimited amount, as long as it's never the exact same mistake?

Re:All extensions disabled due to expiration of intermediate... by eli on Friday May 03, 2019 @11:11PM (#19824156)
Couldn’t disagree more. Do you want to fix the conditions that led to the problem? Or do you view a post mortem as a punitive process?
Re:All extensions disabled due to expiration of intermediate... by mrep on Saturday May 04, 2019 @12:31AM (#19824456)
Can you link to your linkedin profile so we all know who to dox next time you make a mistake? If you have a twitter, please add that as twitter works even better for mobs.

Thanks :)

Re:All extensions disabled due to expiration of intermediate... by Silhouette on Friday May 03, 2019 @11:06PM (#19824132)
Why does someone need to be fired?

That might seem rather extreme, but the fact that this situation was even possible was a consequence of a series of bad decisions over an extended period of time about the required behaviour of new versions of Firefox, combined with technical failures that betray fundamental weaknesses in the whole system design. Whoever was ultimately responsible for those failings demonstrably isn't competent to run something of this importance and should probably either implement immediate and dramatic changes to the relevant policies and technical details or consider their position. Anything less is surely going to damage trust, which is something Firefox can ill afford when it's already in danger of being reduced to a niche product rather than a mainstream browser.

Re:All extensions disabled due to expiration of intermediate... by cheeze on Friday May 03, 2019 @10:59PM (#19824096)
Oh relax. A cert expired. An intermediate cert at that...

This has probably happened to every major cloud provider and countless companies at least once. Certs are hard.

Should Mozilla have had monitoring on their cert expiration? Yes. Will they after this? Probably. Is any one person ever at fault for something like this? No.

Firefox is an open source project. You're welcome to contribute and make things better.

Re:All extensions disabled due to expiration of intermediate... by yjftsjthsd-h on Friday May 03, 2019 @11:43PM (#19824304)
> Oh relax. A cert expired. An intermediate cert at that...

Everyone's extensions broke. Including security ones. Including the ones bundled into the TOR browser. And end-users can't fix it. Because Mozilla decided that it was too dangerous to let users choose what extensions to run for themselves. This is an excellent moment to be upset.

Re:All extensions disabled due to expiration of intermediate... by __david__ on Saturday May 04, 2019 @02:16AM (#19824766)
Being upset is ok! I'm not particularly happy that I can't just override the certificate check on stable. But demanding someone get fired is just pointlessly punitive.
Re:All extensions disabled due to expiration of intermediate... by hnaccy on Friday May 03, 2019 @11:04PM (#19824119)
>Firefox is an open source project. You're welcome to contribute and make things better.

Well no because they won't accept a patch that lets us plebs turn off the signed extension requirement.

Re:All extensions disabled due to expiration of intermediate... by lvh on Friday May 03, 2019 @11:18PM (#19824199)
The Developer edition allows that just fine.
Re:All extensions disabled due to expiration of intermediate... by xena on Friday May 03, 2019 @11:16PM (#19824180)
Alternatively, that person (if they exist) has gotten the best lesson in institutional certificate hygiene rules money can buy. They got their mistake potentially added to hundreds of companies playbooks so it can be caught.

Honestly that's one of the most successful things you can expect out of a failure of this magnitude.

Re:All extensions disabled due to expiration of intermediate... by swiley on Friday May 03, 2019 @10:34PM (#19823983)
I was with you up until you said someone should be fired.

The fundamental problem here is the system (code signing.) It's a political thing with security being the excuse. They want control of a platform for business reasons.

Re:All extensions disabled due to expiration of intermediate... by vladus2000 on Friday May 03, 2019 @11:44PM (#19824307)
Hopefully management being fired. This reeks of management not letting the technical team automate something or other bad decision making that lead to this. If one person was in charge of it and they messed it up, that is as much the fault of whomever gave that important task to only one person as the person making the mistake. I don't want the low-level person punished, I want the one who put them in the place to be able to make such a bad mistake without any sort of redundancy or contingency plan.
Re:All extensions disabled due to expiration of intermediate... by wbl on Friday May 03, 2019 @10:21PM (#19823927)
There is exactly one person who isn't going to do that again.