I agree on everything you said BUT FF needs seriously to stop turning into a chrome clone, it’s insane that i still got java disabled on FF while all is upgraded…
Same with avast: all was fine on 39 version…now i discover this…
Serioulsy why every software rushing to create update that causes merely trouble and issues to us?
Fed up.
In a default install of new releases of Java, it is disabled in all browsers. Oracle was under pressure to do that because of the ongoing security issues with Java. Java can be enabled in the browsers by the Java Configuration utility that any Java installation has. Of course, if the installed Java version is not current or has a known vulnerability, Firefox will disable it per it’s blocklist. https://addons.mozilla.org/en-US/firefox/blocked/
Just updated to FF40. Not even one add on is signed any more ! Currently using the following add ons :
Classic theme restorer ( was not signed before )
Cyscon security shield ( was not signed )
Flag fox ( was signed )
Perfect Redirector ( was signed )
SSleuth ( was signed )
Traffic Light ( was signed )
ublock origin ( was not signed )
Yahoo mail hide Ad panel ( was signed )
You Tube flash player ( was signed )
Firefox 40 does not show -signed after the extension name in the Extensions Tab. However, if you hover the cursor over the extension name -signed should show up in a tooltip. However, very recently update extensions will lose the -signed added to their name but the extension won’t be flagged as ‘could not be verified’ because it is signed. An example is NoScript, which was just updated.
In most of my Firefox profiles, I have only one extension that is flagged as ‘could not be verified’. Extension List Dumper which I modified per instructions found on http://forums.mozillazine.org and bumped the MaxVersion is, of course, not signed. It will be disabled in Firefox 42 unless Mozilla relents. I have RefreshPolicy Continued in a couple of profiles, which is also not signed.
Thanks DavidR for that last post with the attachment that as you say we hope will remain an option available to users to reset to “false” in version 42.
That said, what concerns me when looking at the plans that FF has regarding this quote:
As of [b]Firefox 41[/b] you will not get a warning and [u]unsigned add-ons [b]will be blocked[/b][/u]. [b]There will be a (hidden) preference that you can set to override for the time being.[/b]
As of Firefox 42, unsigned add-ons cannot be used in the standard release (and beta) builds of Firefox. Full stop.
More specifically what concerns me is that it would suggest that the RED part above would be the “the about:config setting” referenced as “a (hidden) preference” that can “override” the requirement “for the time being”. And that I’m afraid that there are possibly plans on removing this setting the way FF42 is described above.
By the time FF 42.0 comes around, I have a suspicion that there are many people using old, no longer undeveloped add-ons who may well come up with ways round this rather than accept that they can no longer use these old, useful add-ons.
Mozilla is beginning to make a series of changes to Firefox that’ll make certain aspects of the browser operate a lot more like Chrome. The changes are broadly designed to make Firefox more secure and stable, but they also have the downside of making it less customizable and potentially more of a resource hog.
If I wanted firefox to look and act more like chrome, I guess I would install chrome (and that for me isn’t going to happen). I just can’t see their reasoning in making browsers unrecognisable from chrome, what’s the point of becoming clones, might as well give up.
As far as resources goes, firefox is already a bit of a resource hog.
Firefox 43.0 is now DISABLING Avast without any ado.
So since August apparently NOTHING has been done on the problem of signature verification.
Furthermore, Firefox advises to contact the manufacturer.
I tried online at the Avast website.
But I need to fill in my order number.
I have no order number.
I do not need an order number.
I am not ordering.
OFF goes Avast with me.
Sorry.
@bob3160: Most new smartphones such as Samsung Galaxy S5/S6. Samsung Galaxy Tab S, and etc the manufacturer Samsung distributes an update. After the update, Intel Security/McAfee gets automatically installed. Will Intel Security also help in protecting users as same as Avast Mobile Security?