Untrusted Status not working

Ask for help about NoScript, no registration needed to post
Guest

Re: Untrusted Status not working

Post by Guest »

Pansa wrote:
Basically currently if you want to set a site to untrusted (or have imported an old rule), chances are it only blocks https.

So your most important steps right now:
1. Fix your default settings to have no checkmarks.
2. Recheck your "untrusted" rules for each entry by switching to trusted, select the red lock and switch back to untrusted.

edit: basically all your "untrusted" rules should have red text instead of black text where the source is named.
Thank you, Pansa! I don't claim I fully understand, but I can follow simple directions, and the urls that were giving me problems are getting under control at last.
Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
NoScriptian

Re: Untrusted Status not working

Post by NoScriptian »

I'm at a loss then. What does Untrusted actually do?
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Pansa
Senior Member
Posts: 318
Joined: Fri Nov 24, 2017 10:30 pm

Re: Untrusted Status not working

Post by Pansa »

NoScriptian wrote:I'm at a loss then. What does Untrusted actually do?
It applies the rules you specified to the source you specified.

Barbaz's resonse was basically pointing out that while you fixed the flawed settings of your untrusted preset (which definitely shouldn't have happened but was true for me, too, to a lesser degree)
When creating the nikon rule, you either forgot to apply the "trusted -> redlock ->untrusted" trick" or something went wrong.

The way it is as you quoted your config, due to the "§" it again only applies to https nikon, instead of both http and https.

From a security standpoint there should not be a single entry in the untrusted preset that has a "§" in front of it, or has black text in the settings UI for the domain name.

edit: A more comprehensive answer:
If you never use the "allow all temp" button, very little. (if you do, it helps not temp allow domains that you KNOW you don't want to also allow by hitting "allow all temp".)
In that case it is merely a visual reminder setting it apart from all the sites that are set to "default", that you already decided on that one.
The third application is for people who aren't AS distrustful. For those the option is to allow scripts in the default setting, and then specifically just un-trusting those pages that they ACTUALLY want to block. So for people who use this actually primarily as a pure adblocker, they would allow scripts by default, and then explicitly killing of the ads, in this not having to deal with every page by default being broken.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Post Reply