Firefox "armagadd-on" issue disappeared by itself (Slackware64 14.2

Moun · 05-04-2019, 03:52 PM

Hello,

My browser was impacted too by the issue, but it disappeared by itself a couple of minutes ago. I didn't do anything, and Studies is not enabled since the option was disabled at the compilation (official package).

I don't understand how it could happen. Any idea?

Paulo2 · 05-04-2019, 06:53 PM

Here was NoScript and some others.
I think Firefox people will release a new version with the fix.

On this post there are some comments saying that the fix through studies
doesn't work anyway.
https://blog.mozilla.org/addons/2019...ns-in-firefox/
There is a comment with a fix by normands-addons but I don't know if we can
trust, so I think it's better wait for the new version.

In the mean time I'm using Seamonkey with old NoScript version and AlienBob's Chromium,
it has NoScript too.

ps. for ESR the 'studies' fix doesn't work for ESR and Android version.

mlangdn · 05-04-2019, 07:33 PM

In about:config, I changed xpinstall.signatures.required from true to false. Problem solved. I don't think it will automatically fix in Slackware.

jmccue · 05-04-2019, 09:10 PM

mlangdn -- saw this on USENET, and works for me. But I probably would not update or add any plugins until the issue is fixed

Looks like once again Linux is SOL, from blog.mozilla.org:

Quote:

Firefox ESR, Firefox for Android, and some versions of Firefox included with Linux distributions will require separate updates. (May 4, 12:03 EST)

chrisretusn · 05-05-2019, 02:11 AM

The "hotfix" does not work here, as expected. It is installed (hotfix-update-xpi-signing-intermediate-bug-1548973) and Active but nothing has changed.

chrisretusn · 05-05-2019, 02:17 AM

Quote:

Originally Posted by chrisretusn

The "hotfix" does not work here, as expected. It is installed (hotfix-update-xpi-signing-intermediate-bug-1548973) and Active but nothing has changed.

Spoke to soon. On a whim I restarted Firefox with Add-ons Disabled, then exited and started Firefox. All is well now. In retrospect it may only be required to exit and start Firefox.

phalange · 05-05-2019, 02:41 AM

I have two add-ons installed, and re-installing one of them from the developer's website reactivated both without further intervention. There was no clear option to re-enable within Firefox.

EYo · 05-05-2019, 04:51 AM

From the bugzilla "fix" link:

Quote:

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled

Normandy sounds like a thing I don't want either, so I "disabled" it too.

https://wiki.mozilla.org/Firefox/Nor...ferenceRollout

Quote:

Feature Flagging with Normandy Pref Rollout

Normandy Pref Rollout is a feature that allows Mozilla to change the default value of a preference for a targeted set of users, without deploying an update to Firefox. This document focuses on the use of Pref Rollout as a mechanism to enable feature flagging in Firefox.

I don't want SHIELD either, why would I?
https://wiki.mozilla.org/Firefox/Shield

Quote:

SHIELD PROGRAM

The Shield platform gives us the ability to push changes in Firefox quickly and with high precision. There are two main goals for the Shield Program.

Shield Turns Superstition into Science
Shield is a Firefox user testing platform for proposed, new and existing features and ideas. Broad Applications The Shield system addon targets specific subsets of users, enables features and messaging, and measures the results of those interventions to evaluate the effect of the features/messages on measures (retention, uptake, performance, crashiness) to create insights for the Firefox product and Mozilla as an organization.

Self Repair
Make it easier for users to recover from common issues. This could be restoring a preference or removing an unwanted toolbar.

No thanks. I guess I have to start re-compiling every update to leave out the Mozilla Protection Racket, or do they not offer to opt out? I see where I can get rid of the google safe browsing in the slackbuild file, but nothing for Normandy or SHIELD.

Perhaps other slackers are just relaxing and enjoying their new corporate overlords. If so, what's in your pipe? Do tell.

Cheers.

jmccue · 05-05-2019, 07:32 AM

EYo - Thanks, by disabled I assume you disabled this in about:config, correct ? (which I just did)

Code:

app.normandy.enabled

Also I noticed 'shield' in about:config seems to be a subset of Normandy, but I am guessing here.

EYo · 05-05-2019, 08:01 AM

Quote:

Originally Posted by jmccue

EYo - Thanks, by disabled I assume you disabled this in about:config, correct ? (which I just did)

Code:

app.normandy.enabled

Also I noticed 'shield' in about:config seems to be a subset of Normandy, but I am guessing here.

Yes that is what I changed to disabled. It's not like I hate the nanny web, but it hasn't protected me from criminals so I'd rather just avoid it myself. YMMV

I know this has been creepy for years, literally. I'm just having another grouchy last straw kinda day. Bah humbug!

Yells at cloud, shakes fist at sky.

ZhaoLin1457 · 05-05-2019, 08:07 AM

Too much paranoia!

I cannot help to not observe that exactly the paranoiacs who mess with the Firefox setup are more affected.

Myself I did not ever noticed that "shocking incident", but I have a life, I have a job and a family to feed. So, I cannot spend all of days around sitting in the front of computer.

And, after all, nobody force you to use Firefox, if you believe that it's a tool of "new corporate overlords"

Skaendo · 05-05-2019, 09:48 AM

Quote:

Originally Posted by EYo

If so, what's in your pipe? Do tell.

Hmmm, I just checked in Waterfox's (56.2.9) about:config for 'normandy' and 'shield' but couldn't find either. But some Waterfox users still might be affected by the "armagadd-on"?

Apparently "shield" is not shipped in Waterfox, as for "normandy" I don't know.

Oh, and cabbage?

EDIT:
Apparnetly Waterfox 56.x.x is based on Firefox 56.x, and Firefox 56.x did not ship "normandy".

Thanks for playing.

EYo · 05-05-2019, 10:44 AM

Quote:

Originally Posted by Skaendo

Apparently "shield" is not shipped in Waterfox, as for "normandy" I don't know.

Oh, and cabbage?

Thanks for playing.

Thanks that was helpful. I'll try building waterfox, it has a nice set of features listed on sbo, might suit my needs... as they are now. Oops, now I see the slackbuild is pre-built binaries. Oh well thanks anyway.

Frop!

And thank you for playing too. Cheers slackers.

Skaendo · 05-05-2019, 11:02 AM

Quote:

Originally Posted by EYo

Thanks that was helpful. I'll try building waterfox, it has a nice set of features listed on sbo, might suit my needs... as they are now. Oops, now I see the slackbuild is pre-built binaries. Oh well thanks anyway.

Frop!

And thank you for playing too. Cheers slackers.

It seems to me, in my amateur view of things, that Waterfox users are seeing some issues if Firefox is installed beside Waterfox. I'm not sure how the two would relate since they have separate profile and install directories. I could be totally off here too.

I have a SlackBuild for Waterfox (complete compile), but it's for -current and I haven't used or updated it for a while. I will upload it to my Hackbuilds.

Moun · 05-05-2019, 03:17 PM

Quote:

Originally Posted by mlangdn

In about:config, I changed xpinstall.signatures.required from true to false. Problem solved. I don't think it will automatically fix in Slackware.

It was fixed automatically here, i's the point of this topic. Seems like I'm the only one :-/