Thanks z3n, much appreciated.
I'm gonna to test that tomorrow and not now since it's in the middle of the night in Sweden.
Anyway, further down there is another script slightly different than one you reposted.
Code:
// For FF < v57 >...?
async function set_addons_as_signed() {
Components.utils.import("resource://gre/modules/addons/XPIProvider.jsm");
Components.utils.import("resource://gre/modules/AddonManager.jsm");
let XPIDatabase = this.XPIInternal.XPIDatabase;
let addons = await XPIDatabase.getAddonList(a => true);
for (let addon of addons) {
// The add-on might have vanished, we'll catch that on the next startup
if (!addon._sourceBundle.exists())
continue;
if( addon.signedState != AddonManager.SIGNEDSTATE_UNKNOWN )
continue;
addon.signedState = AddonManager.SIGNEDSTATE_NOT_REQUIRED;
AddonManagerPrivate.callAddonListeners("onPropertyChanged",
addon.wrapper,
["signedState"]);
await XPIProvider.updateAddonDisabledState(addon);
}
XPIDatabase.saveChanges();
}
set_addons_as_signed();
I really hope this works and if it does then I think the FF support team should consider to use a sandbox and test an update before releasing a bug fix that more than often screw up a lot of things in Firefox.
Of course a sandbox can be used to a lot of things e.g expired certificate.