←back to thread

Firefox 42 will not allow unsigned extensions

(wiki.mozilla.org)
288 points fernandotakai | 2 comments | 11 Aug 15 03:51 UTC | HN request time: 0.412s | source
1. norea-armozel ◴[11 Aug 15 15:04 UTC] No.10041574[source]▶
This is going to be an annoying change me since I use the 1Password extension which isn't signed as far as I know. So, it's likely I'll switch over to Chrome (which I've had performance issues with in the past) or Pale Moon. Seriously, it's my browser. It's fine if you want to make users white list extensions but to completely block unsigned extensions is a bit over zealous. Unless Mozilla makes the signing process automatic (since it seems some extensions on addons.mozilla.org can go months before being updated to the current version) I don't see this working out at all.
replies(1): >>10042027 #
2. Eva_Schweber ◴[11 Aug 15 15:58 UTC] No.10042027[source]▶
Hi. I'm Eva and I work for AgileBits, the makers of 1Password.

I wanted to reassure you that we are working with Mozilla on getting our Firefox extension signed. That will allow you to continue using Firefox as your default browser while still using the 1Password browser extension.