only my trusted sites had been cleared (split from t=25927)

[Gtako]

I am currently having the same issue as OP. Earlier today as i was watching a stream my noscript trusted sites suddenly got erased (My browser had not reset, nothing updated(to my knowledge). I have been using NS for quite a long time so that list was pretty long. Weird thing is that only my trusted sites had been cleared, all of my untrusted sites haven't been touched.

Since then I've updated FX to the latest NS build(78.0b2) and the issue seems to still be occurring. To harp on suggestions/questions previously asked in this thread:

My addon settings do save, even noscript changes seem to change(changed appearance settings)
I do not use Firefox Sync as i never set up a user account, I tried setting up a user account and the settings still do not save.

The Trusted sites seem to be cleared everytime I close Firefox, after i relaunch it the sites ive trusted arent there anymore.

[barbaz]

Do you use Private Browsing at all?

[Gtako]

On my home computer I do not mainly use it, but I do/did use it around the time the trusted list wiped.

[barbaz]

What NoScript version are you using?
Do you see this issue with NoScript 11.0.27rc1?

[Gtako]

I forgot to mention after I first encountered the Issue I had Uninstalled and updated to 11.0.30rc1, where the issue persisted.

I just uninstalled it again and changed it to 11.0.27rc1 where the issue still happens.

[barbaz]

Does this also happen in a new, clean Firefox profile with only NoScript installed?

[Jeff]

It seems I was having the same issue as the OP. It was quite annoying. But at least for me, I could fix it.

First: No, it did not happen in a new, clean Firefox profile with only NoScript installed.
I was seeing the issue with FF 77.0.1, NS 11.0.31, (+some other addons), Win7, not using sync in FF. It started arround the time FF was updated to 77.0 or 77.0.1. I temporarily reverted to NS 11.0.26, but the issue persisted.

The problem seems to be that the NS policy setting "temp" for "DEFAULT" and "TRUSTED" somehow got changed from the original "false" to "true". I don't know how/who/when it changed. AFAIK there is no way to do this using the GUI. The effect is that NS treats all settings for trusted sites as temporary and discards them on shutdown or when revoking temporary permissions.

For me, I fixed this by exporting/editing/importing the NS settings from a file. I changed the following:

Code: Select all

{
  "policy": {
    "DEFAULT": {
      "capabilities": [],
      "temp": true                 <= changed this from true to false
    },
    "TRUSTED": {
      "capabilities": [
        "script",
        "object",
        "media",
        "frame",
        "font",
        "fetch",
        "other",
        "webgl",
        "ping"
      ],
      "temp": true                 <= changed this from true to false
    },
..
}

How did these settings change? Does this fix work for you?

[Giorgio Maone]

It seems I was having the same issue as the OP. It was quite annoying. But at least for me, I could fix it.

First: No, it did not happen in a new, clean Firefox profile with only NoScript installed.
I was seeing the issue with FF 77.0.1, NS 11.0.31, (+some other addons), Win7, not using sync in FF. It started arround the time FF was updated to 77.0 or 77.0.1. I temporarily reverted to NS 11.0.26, but the issue persisted.

The problem seems to be that the NS policy setting "temp" for "DEFAULT" and "TRUSTED" somehow got changed from the original "false" to "true". I don't know how/who/when it changed. AFAIK there is no way to do this using the GUI. The effect is that NS treats all settings for trusted sites as temporary and discards them on shutdown or when revoking temporary permissions.

For me, I fixed this by exporting/editing/importing the NS settings from a file. I changed the following:

Code: Select all

{
  "policy": {
    "DEFAULT": {
      "capabilities": [],
      "temp": true                 <= changed this from true to false
    },
    "TRUSTED": {
      "capabilities": [
        "script",
        "object",
        "media",
        "frame",
        "font",
        "fetch",
        "other",
        "webgl",
        "ping"
      ],
      "temp": true                 <= changed this from true to false
    },
..
}

How did these settings change? Does this fix work for you?

This is an extremely interesting finding, and I've spent the last few hours trying to reproduce and figure out how this could happen, provided that the changes to the incognito UI behavior are actually a plausible culprit for a regression of this kind.
Specifically, I suspected that opening the NoScript Options tab in a private browsing window could and operating on the presets could cause this bug.
Unfortunately (?) that doesn't seem to be the case, at least not in latest version. I'm still checking if that's something like that happened in a previous version and "accidentally" fixed later. Thank you.

[Giorgio Maone]

Bingo! I've managed to reproduce and I think I've fixed it, too.
Can you confirm that

1. you use NoScript in private browsing mode
2. you did NOT check the "Enable setting permanent permissions in incognito/private tabs" option
3. you may have switched some permissions in the popup from a private tab from TRUSTED to CUSTOM (and possibly vice-versa)?

Thanks!

[Giorgio Maone]

Please check latest dev build:
v 11.0.32rc1
============================================================
x [L10n] Updated it, mk, sv_SE
x Fixed setting CUSTOM permissions in private mode may cause
the TRUSTED preset to become temporary
x Updated TLDs
x [XSS] Updated HTML 5 events support
x More compact high contrast appearance

[Jeff]

I can report the following:

1. I always have both private and non-private windows open in FF. I have set NS to be enabled in private mode. I routinely adjust NS settings (mainly via the popup) in both private and non-private windows.
2. I did check the "Enable setting permanent permissions in incognito/private tabs" option in the popup as soon as it was available. HOWEVER, the issue of forgetting trusted sites showed BEFORE this option was even available.
3. Yes, very likely, both directions.

I could reproduce the bug as well doing the following:

• In a private tab, set "Enable setting permanent permissions in incognito/private tabs".
• Set permissions to "TRUSTED" for the site.
• Uncheck "Enable setting permanent permissions in incognito/private tabs".
• Set permissions from "TRUSTED" to "CUSTOM" for the site.
• Select "revoke temporary permissions" in the popup.
• Now all trusted sites have been discarded.

[barbaz]

(Giorgio, while I have your attention , I have a completely off-topic and selfish request:

Removed. Don't hijack other people's threads. Please mind Forum Rules #7. Thanks.

[Guest]

This has started happening for me now that I updated to version 11.0.32, which, apparently, is the version that was supposed to fix this for the above users. I have never had this with any previous version, but it is happening now, with 11.0.32. The whitelist is wiped, and any site added to Trusted disappears after restarting the browser.

[Giorgio Maone]

This has started happening for me now that I updated to version 11.0.32, which, apparently, is the version that was supposed to fix this for the above users. I have never had this with any previous version, but it is happening now, with 11.0.32. The whitelist is wiped, and any site added to Trusted disappears after restarting the browser.

Could you please show us your NoScript Options>Export file content?
Thanks!

[DreamTeK]

Add on settings for noscript are stored in storage-sync-v2.sqlite-wal

Location

Code: Select all

\AppData\Roaming\Mozilla\Firefox\Profiles\dev-edition-default-000\

If you use a program like ccleaner it will clear all sqlite-wal files when clear internet cache is selected.

I haven't done a thorough investigation but I suspect the issue actually lies with FIrefox V79 not committing the changes to the storage-sync-v2.sqlite

You can exclude this file from cleaning by

1. Analysing firefox internet cache in ccleaner

• Double clicking the firefox cache results

• Righ click storage-sync-v2.sqlite-wal and select exclude

Obviously this will make the database cache will no longer get cleaned and may leak websites.