4
exerceo
298d

Add-on signing is censorship in disguise.

Imagine Google could remotely delete YouTube videos you downloaded, to "keep you safe" from the "bad content". Well, Google and Mozilla can remotely disable extensions you installed using their pre-installed trojan horse called "add-on signing".

Always remember, whenever a corporation cites "for your protection", consider it synonymous with "so we can control you more".

Comments
  • 0
    The docs tell you how to disable this or have a plugin signed:

    https://support.mozilla.org/en-US/...
  • 0
    @Demolishun Wasn't add-on signing made mandatory in version 43?
  • 2
    they can download or delete anything from your computer or from your local network if they release update to do so, start from understanding how software execution and privileged escalation works
  • 2
    everything is censorship in disguise if you're paranoid enough.
  • 0
    @tosensei Fair point. But this one doesn't require much paranoia. Now, Google is tackling content blockers. Honestly, I am surprised they didn't do that a decade ago.

    Perhaps because they knew the minute they do this many users would have fled to Firefox.
  • 1
    @exerceo no, users wouldn't have fled to firefox.

    because those users smart enough to actually have a clue what this is about, and the subset of those who actually _give a fuck_ don't use chrome in the first place.

    i'd rather say google simply didn't care before.

    and for the rest, requiring addons to be signed is actually a good thing, so they can't accidentally install their favorite plugin from definitelynotascamsite.com/completelysecurepluginsthatdontcontainmalware/trustmebro.html
  • 0
    @tosensei I checked and the flag to turn it off is there. My guess is that a dev flag so they can test builds quickly.
  • 1
    @Demolishun Since version 43, the flag to turn it off apparently does nothing.
  • 0
    @exerceo interesting. Then how does someone test plugins?
  • 0
    @Demolishun Haven't tried it yet. Perhaps they use Firefox "Developer Edition".
  • 0
    You can recompile Firefox with the check disabled. You can distribute a patch that disables the check. You can distribute a program that downloads the Firefox source, disables the check and compiles it.

    it's FOSS, bitch
  • 0
    you're complaining because Mozilla won't put its developers and logo behind a hazardous product. Literally all you do is complain about brands not distributing hazardous or niche products to the general public. The majority of your rants are about open-source software, or categories in which many popular options are open source. Just stop bitching and PATCH IT.
Add Comment