I have been using Avast free for quite a time now and am delighted with it.
But I keep getting my ankles bitten by surprising events.
I use Chrome as my default browser with no unanswered problems. Firefox is my second choice which I do not use very much, but I do keep it updated.
After a recent Firefox update I found that a world renown AV like Avast had been disabled because it could not be verified. That is so stupid it is beyond my comprehension.
The image alert is shown attached. Could anybody tell me why Firefox should dump a top AV like Avast because Mozilla cannot verify the program ?
Have read the link, but in a nutshell - why is Firefox blocking anything to do with a top rated AV program ? What the hell do they think they are doing meddling about with major AV programs ?
All I wish to know is how to get Avast accepted by Mozilla or dump Firefox in the garbage bin as a failed Chrome look-a-like. I do not need a career in fiddling around with Firefox trying to get my superb AV accepted by their piddling system or reading volumes of posts which do not give a precise answer.
Well if you mean the post by MartinZ, which I did read and says :-
“Hi,
just to confirm, we are working on signing the addon via Mozilla, it should be live before the FF 41 is released.
Martin”
Then as my Firefox is on the update Beta channel and now at version 41.0b5, updated on 30 Aug 15, what has gone wrong with Mr.Martin`s prediction ?
Look, all I want to know is what precisely is going on - a YES or NO answer and not to get involved in past posts and links. At present Firefox is rejecting Avast - why and when will it be corrected ?
No big sweat for a veteran webber, it is only an elementary site advisor like WOT and of no real significance. I would add, that primary sources like Google and Avast should act responsibly when issuing updates and plugins etc. by digitally signing them, so that other primary sources like Mozilla do not reject them.
Recent examples - Avast reject Google and Mozilla reject Avast.
Firefox 41 is still in beta and is not a released version. Firefox 41 will be officially released the week of September 22nd. https://wiki.mozilla.org/Releases
He implied that MartinZ’s assertion that the signing should be done by the time that Firefox 41 was released was not met because he was running Firefox 41 Beta. Beta is not Release version; that was the difference that I was stressing.
I presume that with Firefox released stable versions all would be OK, I would not need to have posted.
I have no idea why my Firefox is a Beta version, I never did it. Somehow my previous stable version has been changed to Beta.
No problem, it works fine and as I do not use Firefox, just keep it as a reserve browser, I think we can forget my inherited muddle.
No problem with my Chrome. But thanks for pointing out that the Beta version is not yet officially released, so Mr.Martin was correct after all. Maybe on the 22 Sept my version 41 will fly OK and the Avast plugin accepted.
Hopefully, Avast will have AOS signed by Mozilla and ready for Firefox 41 official release. If/when AOS is later updated, the signing process will have to be done again. We can only hope. :
