Hacker News new | ask | show | jobs
by cbsks 747 days ago
https://wiki.mozilla.org/Add-ons/Extension_Signing

> Is this a way for Mozilla to censor add-ons they don't like, enforce copyright, government demands, etc.?

> No, the purpose of this is to protect users from malicious add-ons. We have a set of guidelines (https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Revie...) for when it is appropriate to blocklist an add-on and have refused multiple times to block for other reasons.

Is Mozilla refusing to sign the add-on? Or just refusing to host it on addons.mozilla.org? There's a big difference. If the extension can still be signed, it's easy to install on production Firefox builds. If it can't be signed, then it can only be installed on Nightly or Developer builds with xpinstall.signatures.required disabled in about:config.

1 comments

Looks like the extensions are still available in the US: https://addons.mozilla.org/en-US/firefox/addon/censor-tracke... https://addons.mozilla.org/en-US/firefox/addon/%D0%BE%D0%B1%...

So it looks like they are still signed, but they are not available on amo in Russia. The extensions can still be installed on production Firefox builds if they are hosted elsewhere, such as:

Runet Censorship Bypass: https://files.catbox.moe/g7mww2.xpi

Censor Tracker: https://files.catbox.moe/37grym.xpi

Publishing a Mozilla-signed XPI outside of AMO is a breach of ToS, and can lead to being removed from the AMO.
Source? I’m not aware of that restriction.

Self-hosting xpi files is definitely allowed, and all xpi files are signed by Mozilla. https://extensionworkshop.com/documentation/publish/self-dis...

They threatened me here: https://github.com/orgs/ActivityWatch/discussions/818#discus...

See https://extensionworkshop.com/documentation/publish/signing-...

My previous statement was overly broad, but the restrictions do apply to rejected xpis.

So posting the contents of my ~/.mozilla/firefox/default/extensions/ on GitHub is going to remove all of them from the store? Goodness, I wonder why no one thought of that until now.
Yeah sorry I used imprecise language see: https://news.ycombinator.com/item?id=40766705
files.catbox.moe is blocked in russia. You should use litterbox.