5 ms·
Um, Firefox does the same sorts of thing. A) Want to use unsigned addons to play around, or tweak your existing ones[1]? Nope, even if you allow them in about:
by SilasX 7y ago
Um, Firefox does the same sorts of thing.
A) Want to use unsigned addons to play around, or tweak your existing ones[1]? Nope, even if you allow them in about:config, you can't; you have to use a special development version and update it separately.
B) Want to customize your keyboard shortcuts? Sorry, that's not safe, you have to use a crippled API that won't take effect until a given page loads.
C) Want to control your setup? Sorry, their "studies" feature is owned by the marketing team and can make arbitrary changes to the app on the fly, all the way up to its cryptographic infrastructure! (As we learned in the recent add-on mishap [2].)
I use Firefox, but they're not obviously better on these matters.
[1] Like, I don't know, if you made a big deal about underprivileged groups getting into coding, and actually wanted to take the concept seriously rather than just get some photogenic token to write hello-world for a photo op.
[2] https://news.ycombinator.com/item?id=19826827 https://news.ycombinator.com/item?id=19826827
- DaveWalk 7y agoYou raise very good points. The shortcuts thing has made me miserable for years. Surely the coders of Mozilla appreciate a good set of shortcuts, like in whatever IDE they write their code in!
- mook 7y agoDidn't Mozilla promise to publish a post-mortem on the add-on thing two weeks ago? Did that ever happen? Not the CTO post during the issue; the follow up that was supposed to be more technical.
- sebazzz 7y agoYes, they have posted a post-mortem: https://hacks.mozilla.org/2019/05/technical-details-on-the-recent-firefox-add-on-outage/ https://hacks.mozilla.org/2019/05/technical-details-on-the-r...
- mook 7y agoNo, that's the post that _promised_ a post-mortem: > We’ll be running a formal post-mortem next week and will publish the list of changes we intend to make
- gubbrora 7y agoFirefox leaves a lot to be desired, but is still miles better than Chrome.
- superkuh 7y agoThose aren't your only two options.
- BlueTemplar 7y agoWell, there's pretty much only Safari as the remaining option (does it even have a non-Mac version?)
- loudtieblahblah 7y agomight as well be. everything else is based on Chrome/Chromium. Nothing else, other than Firefox, lets me customize in the way Firefox does either. As a security conscious person, this matters.
- superkuh 7y agoFirefox forks.
- MrRadar 7y ago> A) Want to use unsigned addons to play around, or tweak your existing ones[1]? Nope, even if you allow them in about:config, you can't; you have to use a special development version and update it separately. Signatures were mandated for add-ons because there was a plague of malware (or near-malware, such as third party anti-virus software) silently installing add-ons that broke Firefox in various ways. If the end-user could disable that requirement then the malware could do that too. The only way for Mozilla to address the issue was to hard-code the signature requirements. I don't think asking power-users to use Nightly/"unbranded" versions of Firefox to load unsigned extensions is something you should count against them.
- SilasX 7y agoNo, there wasn't. No malware was being spread en masse this way. It was an entirely fictitious threat, as it would have required convincing the user to enter a confusing part of the app (about:config) and correctly change a setting. I can accept that there might have been a malware problem when signatures weren't the default requirement, but that's not the change I'm talking about, where they ignore a user's explicit preference that they're okay with unsigned add-ons. Remember, Chrome allows you to turn off this setting by just flipping a switch into dev mode. Where's the torrent of compromised Chrome browsers from this vector? >I don't think asking power-users to use Nightly/"unbranded" versions of Firefox to load unsigned extensions is something you should count against them. It is when that version doesn't get the same updates and has to be maintained separately.
- MrRadar 7y agoI'm referring to native malware abusing admin privileges to install extensions without the user's consent, not users deliberately installing malware extensions themselves. This was particularly bad in the XP/Vista era (I know I had to remove some rogue extensions from my relative's computers during that time). If the signature check were a flag the malware would just disable it at the same time it installed the extension (remember, it has admin privileges so no user interaction would be required). Additionally, keep in mind that when the signature requirement was added there were still XUL/XPCOM extensions which could hook the browser much deeper than Chrome-style extensions and wreak much more havok.
- loudtieblahblah 7y agoAt least when Firefox has a misstep, it's scope is a lot smaller. Taking a swipe at adblocking, obscuring where you're "logged into the browser" are IMHO - much bigger deals.