They should do manual testing to confirn/deny this, in a mystery customer sort of way.
post
Dude I misread "Mozilla to require data collection in addons", almost dropped my phone
So I can just declare 'none' and happily collect data?
Or is there actually some type of control?
Well, I guess they could. But at least its in the rules and people can report. And if it indeed violates the setting, then the addon could be removed from the repository. So there is an incentive for addon developers not to break that "promise". At least this is the right direction.
Yes, but it's about the tiniest step they could possibly take. It just officially makes violating "trust me, bro" against the rules, but does absolutely nothing to prevent it, nor allow the user to directly prevent such abuse. Some extensions don't need Internet access at all, but there's no (easy) way to stop it from happening. Others only need occasional access for updates, but there's no user control for whether that's all they're doing.
Yes, it also narrows down the number of potential targets for analysis / report. If an extension is not marked "none" then no need to go out of your way to figure out if it does it.
For some extensions it might actually be relatively easy to figure out if they do communicate with an external server that they might not need to, specially considering that the extension format can easily be decompressed, .crx files are just zip files with some javascript and other files inside.. they might want to obfuscate the logic, but it's not impossible to try and unravel things to some extent.
It has been a thing for longer that extensions are not allowed to make connections to the internet, unless it's actually required for the functionality they advertise. And I believe, they have some rudimentary code scans in place to check for that. Besides that, there's also their Recommended Extensions program, where they do thorough code reviews for a subset of available extensions.
I believe it was already required to disclose data collection, except you had to build the UI for that yourself. This makes it easier to comply, and more recognisable for us users.
How about Data-Collection Ban in All Firefox Extensions, Mozilla? How about that?
addons.mozilla.com isn't a large enough source of extension downloads for a lot of extension developpers to be willing to comply with that, they'd just drop the platform, and firefox would have an even harder time getting people to use it.
Hey did the patient on apple‘s crappy idea expire already?
It is possible that any developer could just say "none" even if the extension does collect data? If it has to be manually disclosed, this won't stop malicious actors. Only trustworthy extension developers would disclose this.
Since some extensions are "mozilla-approved", I guess they test it regularly, it wouldn't be hard to verify if one is really sending anything despite their disclosure.
@This2ShallPass @themachinestops As an extension developper on Mozilla's store, yes it's definitely possible. There's some automatic review process but what you state in your implicit data consent disclosure (that's how they call it) is up to the developer.However, the extension can't access all websites unless you specifically allow it while installing. There's an "All websites" permission, so if it's that or if it includes some kind of sketchy site then it's a bad sign.Finally, just like any web page, you can always inspect an extension and check the network requests to see if it's doing malicious stuff. If so, then you can report it.But since mozilla accounts are free and only require a verified email, they could just create another one. It's an endless game of whack-a-mole!
This is a great change. I wonder how long before the hate brigade comes along to complain.
Yup, sounds great to me. I could see a world in which it becomes a bad thing because they try to enforce it by pulling a Google and blocking users from installing extensions that aren't through their official add-on store, but as it is, it's hard to see any reasonable criticism.
It's not clear whether it's a useless disclosure or enforced by the API.
Some extensions have a verified/recommended by Mozilla seal of approval, so these extensions would be checked by a human to see that they comply.
Obviously they can't check every update of every extension in existence, but even just the above is an improvement and certainly not useless.
I don't think this could be enforced by the API without also seriously limiting what extensions can do, which people would go crazy about if they did.
no one ever discloses, they just wait to get caught, then make a new extension and restart the cycle.
The only issue with this otherwise great idea is that "the developer says, that...". A browser API should have a way to only grant certain rights when this is technically disclosed, e.g. an extension can only access location data if this is (formally) declared, and must be able to cope without it if the user or any global policy disallows it.
So, sandbox the extensions, a practical, sensible step on the path to browser as OS (contentious, but doesn't that seem where things are going, and if we lose firefox...). I get it, it's mr right now harm minimization, as opposed to mr right (linux or flatpak) general purpose computers in service of their users with usable security control.
And firefox itself?
I would also like to see a competition to Mozilla itself. One that's fiercely loyal to it commitment to an Open internet.

all 26 comments