NoScript 10 + New Version Releases

Oy vey. RU 10.1.6.3 ?

 

Yes, Version 10.1.6.3.

 

OK, but I wouldn't worry about it.

Bo

 

Krusty, this is really the by the book way of turning Trusted/Untrusted and Custom domains back to Default.

Bo

 

the data file shows black n' red sites "§:googletagservices.com", "googlesyndication.com"

 

To turn "§:googletagservices.com" to Red Untrusted you can do this trick. Go to Options, Trust "§:googletagservices.com", change the lock from green to red, then click to Untrust it, reload. Afterward, "§:googletagservices.com" will be Red Untrusted.

Bo

 

Yes.

 

example of Untrusted https: on my setup that renders black and yes, I can toggle red.
Just sharing.

 

Stable version 10.1.6.4 was released a little while ago .

v 10.1.6.4
=============================================================
x Fixed race condition on XSS filter first load
x Fixed duplicate entries in UI on page reloads (thanks 8-bit
for reporting)
+ Spinner for long sites lists in Options page
- Removed obsolete work-around for accidental TRUSTED preset
wiping
x [UI] Fixed clicking on capability's label doesn't toggle
the related checkbox (thanks dhouwn and olf for reporting)
x [XSS] Fixed false positives on badly encoded URLs (thanks
sage11 for reporting)

https://addons.mozilla.org/en-US/firefox/addon/noscript/versions/?page=1#version-10.1.6.4

Bo

 

Beta version 10.1.6.4rc5 was also released today.

v 10.1.6.4rc5
=============================================================
x Fixed race condition on XSS filter first load

https://addons.mozilla.org/en-US/firefox/addon/noscript/versions/beta?page=1#version-10.1.6.4rc5

Bo

 

Yep, got it.

Bo, is this the correct Default settings?


I thought Default would be the same as Untrusted.

Thanks,
Dave

Edit: It is set the same on my other machine so it must be the default setting for Default. I've disabled those checked boxes so Default is now the same as Untrusted.

 

Hi Krusty, by default, Default comes with frame, fetch and other ticked. Everything else is unticked. You probably made changes to the Default Preset by mistake.

Unticking all Capabilities for Default is fine. Thats how I set mine. It gives you a more restricted experience, you shouldn't have an issue.

Bo

 

Thanks Bo.

Nope, I never made any changes and I had the exact same settings on all three of my machines. I've unchecked them all now anyway.

Cheers,
Dave

 

Krusty, please read reply #11, question C. Probably question A also applies to you (it has to). And Giorgio's reply, #12.
https://hackademix.net/2017/12/04/noscript-quantum-vs-legacy-in-a-nutshell-2/#comment-39677

With earlier version 10, a lot of people changed the allowed capabilities for the Default preset (and other presets as well) by error, some even ticked scripts and then complained that NoScript was not blocking anything, that's why ticking/unticking capabilities was eventually moved from the Drop down menu to Options in later versions (to make it harder changing presets by mistake).

Bo

 

By the way, you can test creating a new Firefox profile, install NoScript, when you go and see what allowed for Default, you ll see frame, fetch and other ticked, nothing else.

Or, if you are using Sandboxie, click Reset while running Firefox sandboxed, look at the Default Preset, confirm and delete the sandbox.

Or, if you are not using SBIE, Export settings to create a backup, click Reset, look at the Default Preset, confirm, Import Settings back.

Bo

 

What ever, Bo. I made no changes and all three machines were the same, maybe carried over from an earlier version, but I didn't change them.

 

My God that UI looks like ****.

 

Regardless of your biased opinion, NoScript makes Firefox the best browser by far and continues to be the best addon in the world.That's my opinion.

Personally, I am not into pretty UIs, look at Sandboxie, it uses same UI as it did 10 years ago and also get knocks all the time about it, but NoScript like SBIE, works great which is whats important and what matters.

Bo

 

It would seem we both have biased opinions

 

That was exactly.....my point.

Bo

 

Cool - we're on the same page.

 

A couple of betas were released today (10.1.6.5rc2/10.1.6.5rc1). I am up to 10.1.6.5rc2, its working fine.

v 10.1.6.5rc1
=============================================================
x Fixed "XSS User Choices" not being included in Export files

v 10.1.6.5rc2
=============================================================
x [XSS] More specific and unobtrusive handling of window.name
sanitization

https://addons.mozilla.org/en-US/firefox/addon/noscript/versions/beta?page=1#version-10.1.6.5rc2

Bo

 

Betas from the last few days. New option to open NoScript Menu via right clicking a web page and selecting on context menu works fine

v 10.1.6.5rc4
=============================================================
+ Context menu on web pages to access main UI
x Fixed UI regression showing only the two rightmost
components of IPv4 addresses

v 10.1.6.5rc3
=============================================================
x [XSS] Better ordering of window.name sanitization

https://addons.mozilla.org/en-US/firefox/addon/noscript/versions/beta?page=1#version-10.1.6.5rc4

Bo

 

A new beta is out (10.1.6.6rc1).

v 10.1.6.6rc1
=============================================================
+ Tabbed options sections
+ Appearance option to turn off script count badge
+ Appearance option to hide context menu item
x Fixed legacy import bug creating too permissive DEFAULT
presets (thanks Grumpy Old Lady for reporting)
x Fixed 10.1.6.2 regression: enabling object placeholders
affected DEFAULT permissions (thanks Pansa for reporting)

https://addons.mozilla.org/en-US/firefox/addon/noscript/versions/beta?page=1#version-10.1.6.6rc1

Bo