NoScript 10 + New Version Releases

NoScript v11.0.41 Released (August 25, 2020)

Download - Firefox (AMO)

 

NoScript v11.0.43 Released (September 8, 2020)

Download - Firefox (AMO)

 

NoScript v11.0.44 Released (September 15, 2020)

Spoiler: Changes v11.0.44

v 11.0.44
============================================================
x Dispatch synthetic SVGLoad event in soft load when needed
x [L10n] Updated da, es
x Fixed namespacing issues with script replacements
x Fixed media placeholder not shown when blocking Youtube movies
x Work around for unpredictable content script execution order
x Ensure content of NoScript prompts is always visible
x Fixed soft reload messing with non UTF-8 encodings (thanks "Quest" for reporting)
x Updated TLDs
x [XSS] Fixed escape detection bug causing strage false
positives (thanks Dave Howorth for report)

Download - Firefox (AMO)

 

NoScript v11.0.46 Released (September 18, 2020)

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

NoScript v11.1.1 Released (October 6, 2020)

Spoiler: Changes v11.1.0 & v11.1.1

v 11.1.1
============================================================
x Updated TLDs
x Better heuristic to figure out missing data while computing contextual policies
x Fixed regression breaking per-tab restrictions disablement (thanks Horsefly for report)

v 11.1.0
============================================================
x Improved blocking of media documents unaffected by webRequest
x Automatically init tag message with last changelog
x Improved NOSCRIPT element emulation compatibility with XML documents
x webNavigation.onCommitted + tabs.executeScript to deliver DOM policies earlier whenever possible
x Partial work-around for Fx 80 file:// documents parsing inconsistencies (further fix for issue #156)
x Cache policy on top document for file:// subdocuments (fixes issue #156)
x Enforce more restrictive CSP on media/object documents
x Better cross-browser media handling
x [Mobile] Use tabs as prompts if the browser.windows API is missing
x Fix browser UI for image, audio and video content being partially broken on file:// URLs
x Normalize file:// directory paths on Firefox
x Allow browser UI scripts for file:// directory navigation
x Updated TLDs
x [L10n] Updated mk

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

NoScript v11.1.3 Released (October 9, 2020)

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

NoScript v11.1.5 Released (November 6, 2020)

Download - Firefox (AMO)

 

NoScript v11.1.6 Released (December 9, 2020)

Spoiler: Changes v11.1.6

(cc @lastknight, @raistolo)v 11.1.6
============================================================
x Better handling of concurrent prompts issues (thanks billarbor for reporting)
x Remove z-index boosting from ancestors when placeholder is collapsed or replaced (issue #162)
x Fixed permission keyboard shortcuts being triggered with modifiers like CTRL (thanks barbaz for report)
x More accurate blockage reporting, with better filtering of page's own CSP effects
x [UI] Fixed bug in CUSTOM sites filtering (thanks barbaz for reporting)
x Fixed bug in automatic HTML events build-time updates
x Updated HTML events
x Updated TLDs
x [L10n] Updated sv_SE
x Better handling 0 width / 0 height media placeholders

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

NoScript v11.1.7 Released (December 21, 2020)

Spoiler: Changes v11.1.7

v 11.1.7
============================================================
x Optimize serviceWorker tracking for heavy tabs usage (thanks vadimm and barbaz for investigation)
x Force placeholder visibility on Youtube embeddings
x Fixed popup opening being slowed down if options UI is opened (thanks Sirus for report)
x Explicit failure for wrong settings importation formats
x Updated TLDs

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

NoScript v11.1.9 Released (January 17, 2021)

Spoiler: Changes v11.1.9

v 11.1.9
============================================================
x Return null when webgl is not allowed (thanks Matthew Finkel for patch)
x [XSS] Fixed memoization bug resulting in performance degradation on some payloads
x [XSS] Include call stack in debugging log output
x [XSS] Skip naps when InjectionChecker runs in its own worker
x Shortcut for easier XSS filter testing
x More lenient filter to add a new entry to per-site permissions
x [L10n] Updated de
x Replace script-embedded bitmap with css-embedded SVG as the placeholder logo
x Updated TLDs
x Remove source map reference causing console noise
x Fix per-site permissions UI glitches when base domain is added to existing subdomain (thanks barbaz for reporting)

Download - Firefox (AMO)
Download - Chrome (Web Store)

 

Anyone else notice that after trusting JavaScript for a site, the next time you visit that site it is no longer trusted? I have trusted most JavaScript I need for most sites I visit but lately any new JavaScript on sites seem only temporarily allowed even though I specifically chose to trust it.

 

Hi Krusty. I don't have issues with NoScript 11.2. Perhaps your NS settings got corrupted, it can happen.

Hopefully you keep backups of your NS settings. If you do, you can try (first) importing your backup. If the issue continues after doing that, then do a NoScript Reset (second option to try), and import the settings. If that doesn't work either, then I would uninstall NS and reinstall it, and import the backup.

Bo

 

Thanks Bo,

I know you have NS trained well, but just to confirm you're not seeing this bug could you please visit an unfamiliar website of your choice, allow first and third party JavaScript required for that site to work correctly, then after closing Firefox please navigate back to that site and check if the third party scripts are still allowed.

Thanks.

 

Even though I haven't experienced anything wrong since updating to NoScript 11.2 on the 4th of February, I went ahead an did what you are asking before posting my earlier reply. There is nothing wrong.

But you might have, like I said, a case if corrupted settings. When that happens, you experience things similar to what you described.

Another thing. Sandboxie? If you are using SBIE, you need to allow Direct file access to a few files in Firefox, otherwise changes in NoScript don't survive closing the browser/sandbox. I am not sure if you are using SBIE, let me know so I tell you what this files are. I don't allow access to this files in my everyday Firefox sandbox but is good to have one sandbox were changes in NoScript are allowed out of the sandbox.

Bo

 

Don't use and have no interest in Sandboxie of any flavour, so that isn't related.

What ever the bug is it has started on both of my Win10 machines at the same time. If it is corrupt settings then weird that both machines became corrupt at the same time.

Oh well, I'm not going to lose sleep over it, but if NS bugs me enough I will have no problem disabling or removing it from both machines.

Thanks Bo, have a great weekend!

 

I wasn't suggesting for you to take on Sandboxie but had to ask since using SBIE could explain what you describe.

If it started happening in both computers at about the same time, look for something in common that those computers have. It could be another content blocker or extension that is conflicting with NoScript.

Why giving up that easy, you should at least try creating a new Firefox profile or import old settings. NoScript is worth the effort of trying to figure out why you have a problem. If you don't feel that way, then I agree, perhaps removing it is your best option (as you said).

Take care Krusty, wish you a nice weekend also.

Bo
.

 

I had the same problem awhile back and found that CCleaner was deleting the file "C:\Users\User\AppData\Roaming\Mozilla\Firefox\Profiles\xxxxx3x.default-release\storage-sync-v2.sqlite-wal" and "C:\Users\User\AppData\Roaming\Mozilla\Firefox\Profiles\xxxxx3x.default-release\storage-sync-v2.sqlite". I excluded both files in CCleaner and now settings are saved in NoScript. That may not be the same problem as yours but just letting you know my experience with NoScript. Good luck.

 

Awesome! That did the trick.

I just excluded those files in Privacy Eraser and the site was still in the Trusted list. I shall do the same with CCleaner, but I don't use it that often these days.

 

Good to hear. Glad I could help.

 

Yes, thank you very much for that, I would never have found that for my self. I'm glad it was something so simple.

 

I had forgotten about those exclusions. They being in use for a while now. In addition to the files Wlfrun mentioned, I also exclude in CCleaner storage-sync-v2.sqlite-shm. Perhaps excluding this particular file is not needed but I am doing it.

Bo