2 ms·

Librefox isn't exactly what you described, but it's close. It's a set of configs that disable a bunch of telemetry and other unauthorized mothership connectivit

Librefox isn't exactly what you described, but it's close. It's a set of configs that disable a bunch of telemetry and other unauthorized mothership connectivity and settings pushing. https://github.com/intika/Librefox https://github.com/intika/Librefox However, Librefox is only Firefox with some configuration changes. It is not a whole new build, and it wouldn't have protected you from this problem since the problematic addon cert checking is still there. Note that this would have happened even if the browser never communicated back home - this problem was triggered via an unwitting time bomb of sorts, not because Mozilla actively took an action that inadvertently broke something.

dingo_bat 8y ago
> Note that this would have happened even if the browser never communicated back home - this problem was triggered via an unwitting time bomb of sorts, not because Mozilla actively took an action that inadvertently broke something. I was never worried about Mozilla's telemetry. I happily enabled all feedback/telemetry options because I genuinely wanted them to fix any problems. I understand that this problem is not caused due to phoning home. The decision process that led them to make it impossible to load an extension without it being signed by them is problematic. It means that I don't trust them with all my debugging data. I don't know what other time bombs are hiding inside the code. What would happen if Mozilla ceased to exist tomorrow? Will existing firefox installs get bricked after some time? Even big bad Microsoft allows you to install unsigned hardware drivers if you dismiss the scary warning.