3 ms·
Developer Edition and ESR (behind a flag) support unsigned extensions [0]. It's not possible to self-sign them, and standard release Firefox won't accept them (
by 0x_rs 4y ago
Developer Edition and ESR (behind a flag) support unsigned extensions [0]. It's not possible to self-sign them, and standard release Firefox won't accept them (there's also unbranded builds that do not verify signatures). I don't like it myself, but whenever I recall the absurd amount of malicious addons that would install themselves in browsers up until about a decade ago into the average person's PCs, I think it's a fair decision, but development of web extensions is still a massive pain. If the removal is not undone, I think they'll be asked to take down the signed xpi they're hosting like [1] were.
>Self-distributing a version that we rejected due to policy violations is circumventing our review process and our policies. We ask that you stop self-hosting rejected and/or violating versions immediately (by Friday, Dec 2). Otherwise we might have to block your add-on from running in Firefox.
0. https://wiki.mozilla.org/Add-ons/Extension_Signing https://wiki.mozilla.org/Add-ons/Extension_Signing
1. https://github.com/orgs/ActivityWatch/discussions/818#discussioncomment-4017528 https://github.com/orgs/ActivityWatch/discussions/818#discus...
- josephcsible 4y ago> >Self-distributing a version that we rejected due to policy violations is circumventing our review process and our policies. We ask that you stop self-hosting rejected and/or violating versions immediately (by Friday, Dec 2). Otherwise we might have to block your add-on from running in Firefox. Blocking a sideloaded add-on from running for any reason other than it being unambiguous malware world be a major abuse of power and breach of trust on Mozilla's part.