Chris "Slarti" Pinard (slarti) wrote in ljlogin,
Chris "Slarti" Pinard
slarti
ljlogin

Ffffffff---irefox 43

So, you may have heard that Firefox 43 is out. If you've upgraded to it, you may have noticed that LJlogin stopped working. That's because of the magic of extension signing! As that page notes, Firefox is moving in a direction where they require all extensions to be signed by AMO (addons dot mozilla dot org), regardless of whether or not you're actually hosting the extension at AMO or on your own server like I am with LJlogin.

I'm not really especially opposed to the concept in theory. I only get cranky because of two particular points:

  1. Signing requires that you submit the extension for code review, which I am also not really opposed to in theory, but I know in my heart that there's no way in hell that LJlogin 2.x's code will pass any sort of review, and I'm still (yes, after so many years, I know) a sizable number of steps behind even beginning on the 3.x rewrite.

  2. Their eventual goal is that you won't be able to override the signing requirement, at least in the standard browser (more on that in a moment, or in the link above), which finally is a point that I am actually opposed to.

The good news is that in Firefox 43, you can still override the signing requirement by going into about:config and toggling xpinstall.signatures.required to false. As noted in the above link, however, Firefox 44 will remove the option entirely. At that point, in the high likelihood that I haven't miraculously manifested LJlogin 3.x out of thin air, your choices will be to either not upgrade (which I acknowledge is a security risk) or switch from the standard browser to the developer or unbranded editions (which I don't really know anything about yet, but presumably should be fine), which will keep the setting you can override.
Subscribe
Comments for this post were disabled by the author