Mozilla (maker of the Firefox browser) has updated their code signing requirements for
extensions installed in Firefox.
Important dates/releases pertaining to this issue:
· Firefox 41 (current release) and 42 (current beta) - Firefox warns about signatures but does not enforce them.
· Firefox 43 scheduled for release on December 15, 2015 - Firefox will
have a preference to disable signature enforcement (signature enforcement will be enabled by default).
· Firefox 44 scheduled for release on January 26, 2016 – Firefox will not allow unsigned extensions to be installed.
What does this mean to you?
If you are running Covenant Eyes v5.4.3 or earlier for Windows or Covenant Eyes v2.8.3 or earlier for Mac with Firefox 41 or later, the Covenant Eyes extension may be disabled and you will not receive the latest version of Covenant Eyes reports.
You can verify the version of Covenant Eyes for your computer by clicking the Covenant Eyes menu icon and selecting “About Covenant Eyes” from the menu.
You can install the latest version of Covenant Eyes from My Account. There is no need to uninstall Covenant Eyes prior to installing the latest version from My Account.
I am sorry you have had trouble with Magic Jack and some versions of Covenant Eyes for Windows. We are working on a version that addresses how Covenant Eyes interacts with DNS settings and may solve the conflict that you had between Covenant Eyes and Magic Jack.
Feel free to contact me at email@example.com if you would be interested in testing the new build once it is available. It is our desire to ensure that you can use the latest version of Covenant Eyes alongside the latest versions of other programs on your computer.
- Install the Non-DNS version of Covenant Eyes when it is available will to see if this version work more effectively for you. Installing this version will not require uninstalling Covenant Eyes.
- Continue using Firefox v45 or earlier until you are no longer required to use Covenant Eyes. You can disable Firefox upgrading here: https://support.mozilla.org/en-US/questions/939518
Right now Firefox is at 45.0.1 and the XPI is at 0.8.1, and again, so far so good. I'll leave the test machine on for a day or so before sending over to my main computer.
Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to TRUE in the Firefox Configuration Editor (about:config page). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.
Once you open that "editor" page, search this string "xpinstall.signatures.required" and then once it pops up, RIGHT click on it (the only entry) and TOGGLE it back to "TRUE" as it says above.
So as this workaround is not needed anymore if you have the new SIGNED XPI file. So until the non-DNS version 6.x of C/E is released, this will get the USB MagicJack users running without any Firefox issues when Version 46 of Firefox comes out in April.
Meanwhile Alpha testing of C/E v6 is going well. I'm going to run the MJ on my main machine for a few days to verify 0.81XPI is nice with older C/E reporting on Tuesday for me. I'll switch the MagicJack back to the ALPHA test machine after the report is generated.
Hope this helps in meantime.
It is against the Covenant Eyes mission and the interest of our customers to perpetuate the life of old versions rather than apply those fixes in the latest version. Doing so would put our customers at risk because of known issues with those old versions, and divert resources from improving the current versions. As a result, I am unable to procure the development resources necessary to get and release a separate Firefox XPI package.
We recommend that you continue using the beta version we provided to you. We are currently focused on the next CE release which will have an impact on a large number of Covenant Eyes users. We hope you will understand our need to prioritize our software updates based on the benefits and impact to the entire CE community.
Again, and I repeat above for security's sake, if a user has toggled the override of signed extensions to "false" in Firefox, they need to restore it to the original "true" value whenever they update their extension to C/E's newer signed version.