Important Extension Info for Firefox Users!

  • 4
  • Problem
  • Updated 4 years ago


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.

Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
  • We've got you covered!

Posted 4 years ago

  • 4
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
I run Covenant Eyes v5.2.106 out of NECESSITY because I run a Magic Jack phone on this computer using the USB port. Any later version of C/E completely negates the use of the phone. And I mean completely. So where does this leave me? I need my phone. I need my computer. I need Covenant Eyes, and I need Firefox to work all at the same time. I found this out the hard way when upgrading FROM v5.2.106, and had to deal with MagicJack with a friends phone as mine particular jack did NOT do Ethernet. That was quite annoying until I went back a version of C/E to v5.2.106 and everything started working perfectly again. Guess I'll be staying at Firefox 41.0.1 then. At this point with Extension 0.7.3 dated March 19, 2015 all I get is a warning in add-ons manager that "the Covenant Eyes add on could not be verified, proceed with caution." It is still enabled, and seems to be functioning.
(Edited)
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Hey Chris,

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 windowsbeta@covenanteyes.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.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Well, it just happened. Firefox went to 43.0.1 and DISABLED Covenant Eyes for Firefox V0.73, BUT, there is a "non warranteed" workaround. Follow this page inside Firefox: https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct#w_what-...
And this part:
Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to false 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 to "false" as it says above. It will then have to RESTART Firefox, but, any and all non-signed add-ons will ENABLE, even the ones you DON'T WANT that were previously DISABLED purposely. You will need to verify which just were re-enabled at your own risk. Hopefully, only C/E was the only one DISABLED on this Firefox update and was the only one restored.
Hope this helps, and BTW, when is there going to be a USB MagicJack version ready? Basically, if not, let me have my DNSs to myself which I think is the major USB MagicJack downfall. I've been using SymantecDNS values of 199.85.126.10 and 199.85.127.10 forever. Since the version of C/E after mine you've apparently usurped DNS to 127.x.x.x and USB MagicJack doesn't like that value apparently. Maybe C/E can "look" for a manual entry of the Symantec values and "allow" them without having to then automatically reissue the 127 net values?
(Edited)
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Chris,

Thanks for the update. We have made significant progress toward a Covenant Eyes for Windows client that does not change your DNS settings. I would be happy to contact you once a beta is available for download if you'd like.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Please do Aaron. Especially if the ports that Magic Jack use are "opened" for the USB version of MJ. From a chat with MagicJack reps: "You can try to ask them if they can open 2 XXX ports xxxx - xxxx on that software." Which I think is easily done with a hardware search for "YMAXCorp magicJack CD USB Device" or equivalent Ymax name under DVD/CD ROM drives in Device Manager when C/E loads. Then once this is established, just open the MJ ports. Even if NOT signed in. This will let the phone work in case of 911 emergency, which is my ultimate complaint. God forbid there is an emergency and the computer is on and C/E is not logged in. Those ports are held closed and the phone is denied usage. If C/E is "smart" enough to see the fact that a USB MJ is physically present it can "allow" those two specific MJ-needed ports be open for the USB MJ even while NOT logged in. I think it quite prudent for this to save lives. I've been complaining for years now about this. I've kept the port TYPE & numbers above blank here because this is a public forum. Please email me direct (user=NYgnat) for the port numbers, or look to previous issues on my account history for the port numbers. Thanks, Chris.
Photo of Kristina Schmidt

Kristina Schmidt

  • 1 Post
  • 0 Reply Likes
We've actually been forced to uninstall/reinstall recently on some of our computers because it would say it was updated when it wasn't.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Uninstall/reinstall which program? If it was Firefox, see above to "get over" on the way FF needs to have updated Extensions. I'm still using C/E v5.2.106 with Extension 0.7.3 with FF v43.0.3 without a problem. Magic Jack working also. Hope that helps.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Aaron, is there a way to get the Covenant Eyes for Firefox v.0.7.3 "Add-on" so that IT ALONE is now "signed" to work with the old C/E version 5.2.106? Maybe just name the "signed" version v.0.7.4? We might be able to make a "kludge" fix before a full C/E release fixes the MJ DNS-deny issue?
(Edited)
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Getting kinda close now, FireFox just went to v45.0 today 3/9/16 and v46 will NOT ALLOW the workaround in the first posting to allow unsigned ANYTHING so I will be completely sunk at that point. I will have to stay where I am at Firefox 44.0.2 while using my MJ to play it safe.
Aaron, PLEASE HELP!
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Chris, 

My apologies for not responding sooner. I have had some discussion with the team here at Covenant Eyes concerning your situation via email. I will bring this up again today to determine the best plan of action for you and others who may face a similar situation. Just as a heads up, according to the Mozilla wiki, Firefox v46 will be released on April 19, 2016.

We will be and have been working on releasing an adequate solution toward a non-DNS build of Covenant Eyes for Windows as quickly we can. We currently have an internal build that we are testing. I will keep you up to date on the progress of this as it becomes available to me.
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Just a quick follow up to my last reply on this thread. We are still working toward a non-DNS version of Covenant Eyes. In the mean time the following options are available for Firefox users.
  • 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
I currently do not have a release date for the next update for Covenant Eyes as it is still in testing. Thank you for your patience as we work to providing the best possible solution for our members.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
When I free up a test machine to set up the pre-beta I will test that version. I'm not rocking my existing machine's boat so-to-say. I've already let my accountability partner know of a future UNinstall of that pre-BETA test version when complete and that entire dialog. Hopefully in a few days I'll get to it.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
So far, ALPHA testing on the 6.0.5 version is going well. C/E and MagicJack software still "fight" when they both are loading simultaneously, but that has ALWAYS been an issue. The test machine is a 3.06GHz P4HT with 2GB RAM. Nothing else running on it. If there was a way for C/E to force itself higher up the "pecking order" of the program loads in start up such that it precedes MJ's softphone's loading, that may help matters on the contention issues at initial loading. One of the programs usually fails and resets, then after that failure they "play nice."
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.
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Thanks for the update, Chris!
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
NEW update 3/26/16, interim fix for MagicJack users STILL running C/E v5.2.106 with Extension 0.7.3 out of necessity.... There is a VERY SIMPLE workaround that DOES actually work and has been verified by me personally also. The only catch is that Covenant Eyes has to make the NEWEST Firefox 0.8.1 XPI "plug in" file available SEPARATELY for download. (Aaron- Maybe as an attachment/link in this forum? And, BTW Aaron, you might want to rename this forum from "Important Extension Info for Firefox Users!" to "Important Extension Info for Firefox Users - including issues for USB Magic Jack users!" on the download page it states just "Using Firefox as your primary browser?" You might add something about USB MJs issues too, which I'm covering.) When you install this new XPI file, you actually need to go back above and toggle the override BACK TO TRUE if you did it already above to FALSE:

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.
(Edited)
Photo of Aaron

Aaron, Official Rep

  • 41 Posts
  • 1 Reply Like
Thanks for keeping us apprised of your testing with the Covenant Eyes extensions and the issues you have concerning Magic Jack.

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.
Photo of Chris

Chris

  • 12 Posts
  • 1 Reply Like
Aaron, I think you misunderstood MY mission. This was meant ONLY as a stop-gap until v6 of C/E was fully released in a few weeks. It was specifically directed for people stuck in my predicament still REQUIRED to use the old version of C/E to use their MagicJacks in USB mode. Once C/E v6.x is fully released, I believe all the MJ and Firefox issues will be resolved as you say. I look forward to that release.
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.
(Edited)