Forbidding a domain makes it Untrusted

Ask for help about NoScript, no registration needed to post
nmb3000
Posts: 4
Joined: Tue Dec 11, 2012 2:34 am

Forbidding a domain makes it Untrusted

Post by nmb3000 »

After allowing a domain (temporary or permanent), if you go into NoScript's menu and click "Forbid domain.com", that domain is added to the Untrusted list and no longer appears in the menu and also is not allowed if you "Temporarily allow all on this page". It used to be that to mark a domain Untrusted you had to go into the Untrusted menu and click "Mark domain.com as Untrusted".

I'm not sure when it changed, but this is frustrating behavior. It used to be that clicking "Forbid domain" did not add domains to Untrusted. It would simply put them back to a "not-allowed" status (as if they were neither Allowed nor Untrusted). Also, as it works right now, I see no way to put a domain back into this "not-allowed status" state once it has been Allowed or Untrusted. You also cannot remove a domain from the temporary/permanent allow list without putting it into Untrusted.

Is the new behavior intended?

Thanks!
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0
User avatar
Giorgio Maone
Site Admin
Posts: 9557
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Forbidding a domain makes it Untrusted

Post by Giorgio Maone »

This is the normal behavior if you (accidentally) choose "Allow scripts globally".
Otherwise, please check whether your noscript.forbidImpliesUntrust about:config preference is still false as it should be.
If it is, please export your configuration (NoScript Options|Export) and mail me, thank you.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0
nmb3000
Posts: 4
Joined: Tue Dec 11, 2012 2:34 am

Re: Forbidding a domain makes it Untrusted

Post by nmb3000 »

Giorgio Maone wrote:This is the normal behavior if you (accidentally) choose "Allow scripts globally".
Ah, that probably explains it. I don't allow scripts globally, but on my work computer I have "Temporarily allow top-level sites by default" enabled because it makes my job a lot easier and script concerns are less of an issue. forbidImpliesUntrust is still false.

May I ask why there's a difference between the two modes?

Thank you for your time.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0
User avatar
Thrawn
Master Bug Buster
Posts: 3106
Joined: Mon Jan 16, 2012 3:46 am
Location: Australia
Contact:

Re: Forbidding a domain makes it Untrusted

Post by Thrawn »

nmb3000 wrote: May I ask why there's a difference between the two modes?
Because if you're globally allowing scripts, or if they are automatically whitelisted when you visit them, then the only way to block them is to mark them as Untrusted.

And the reason that global allow works this way is because marking as Untrusted is supposed to mean, "I will never want to whitelist this site, please take it off my menu," so it gets blocked even when all other sites are allowed.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.

True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0
Post Reply