Or maybe only install extensions from trusted
sourcesdevelopers.I think the point is that even if an extension comes from a trusted source, the developer could fairly easily push out an update that turns the extension into malware. Check the GitHub link in another comment below where the developer posts the solicitation emails he gets on a regular basis offering to monetize his extension. He isn’t selling out, but maybe not every dev is as willing as he is to forgo a potentially lucrative offer.
And there are cases where this has already happened: https://www.bleepingcomputer.com/news/security/-particle-chrome-extension-sold-to-new-dev-who-immediately-turns-it-into-adware/ There are probably more recent cases too, but this was the first one I could find.
To be specific: from trusted developers. Installing them only from the official repository (is it still possible to reasonably install them any other way?) won’t help if a dev sells such an addon. On the other hand I cannot imagine someone like Raymond Hill (the uBlock Origin dev) doing it, considering his track record.
Yeah, that’s what I meant.
Firefox will disable extensions in private mode if you want to
deleted by creator
I love the offer of almost $15k to then say they can bargain if the users are active, like if it’s worth that much without active users then that’s definitely shady.
It’s interesting to read as I never thought about the vulnerability these extensions are.
I guess you should limit the number of extensions you have.
Exactly why most enterprise organizations disable them. You should too if you’re doing anything sensitive data.
That’s why on my work PC I use a completely vanilla Firefox, gotta live with the ads. But I’m not risking giving full access to website content to any extension
It would be nice if Firefox built in something like GreaseMonkey to allow for some things to be added by the user, while still having full control over the code. Arc has this, but it Chromium based, Mac only, and doesn’t allow you to get your data (like bookmarks) out of it very easily.
To add to the blog post, if you use user scripts, utilize your manager’s blacklist and learn REGEX.
If needed, use Group Policy, Regedit or .plists on macOS to blacklist domains to prevent an extension from running on them. As an example, I use Shutup.css to block comments online, but on something like Lemmy, I want to see comments as that’s primarily how content is created and adding it to my extension domain blacklist prevents the extension from running on the website or any lemmy domains.
deleted by creator
I thought my ISP already had this data and is selling it. Should I go make sure all my extensions are 100% kosher?
Your ISP cannot read https data in transit. Extensions can because the page is now rendered on your local browser.
Thank you!
