Page 1 of 1

return protection to maximum

Posted: Tue Aug 09, 2016 6:29 am
by davoid
Hi,

I was tired of allowing individual scripts to maintain functionality of webpages, so I went to disable the addon.
There was an option dialog that said I could have still protection, so I chose that.
But now I want to return to the default settings I had before, but I do not know how to do it.
I want to keep the existing permissions that I set previously for frequently visited websites, so I don't want to do a reset.
Any help appreciated.

Thanks,
Davoid.

Re: return protection to maximum

Posted: Tue Aug 09, 2016 2:57 pm
by barbaz
NoScript menu > Forbid Scripts Globally
*or*
NoScript Options > Whitelist, un-check "Scripts Globally Allowed (dangerous)"

Re: return protection to maximum

Posted: Sun Aug 14, 2016 6:11 pm
by swj
I'm having a similar, but slightly different problem. I was trying to troubleshoot some issues where I had to verify my account with a 3rd party website in order to use the website I wanted, and during my efforts I temporarily allowed scripts globally (after trying to allow many individual parameters first). Anyway, when I was done troubleshooting, I tried to revert back to globally forbidding by unchecking the "Scripts Allowed Globally" box in the whitelist tab, however Noscript is still allowing globally (despite restarting firefox). Also, the menu is not showing all of the options when I click on it (even though the boxes for them are checked in the appearance tab). Any ideas on what I am missing to restore global forbidding and get the menu to display properly again? Thanks so much!

Re: return protection to maximum

Posted: Sun Aug 14, 2016 6:32 pm
by barbaz
@swj: Are you sure your un-setting of Scripts Globally Allowed actually stuck? As in, were scripts not globally allowed between when you un-checked the setting and when you noticed scripts were globally allowed?

Re: return protection to maximum

Posted: Sun Aug 14, 2016 8:52 pm
by swj
@barbaz Not sure I completely understand your question, but Noscript was definitely globally blocking before I started troubleshooting, and was definitely globally allowing when I allowed it during troubleshooting. The trouble started when I tried to go back to globally blocking, and it's confusing on what it is actually doing now. When I go to any page that I haven't visited since this began, any scripts that were previously white-listed for that page are still allowed, but so are any others that I haven't already marked as untrusted (which is what I have been doing to block them in the interim at the moment) on other pages that I visited since this change. And when I bring up the contextual menu, there's no option for temporarily allowing anything in the "untrusted" list. And considering that the status bar label says that scripts are currently allowed, its seems like it's globally allowing everything that I haven't untrusted in the meantime. But when I go the options menu, the box for Scripts Allowed Globally (dangerous)" is unchecked. And if I check it, then the behavior doesn't actually change. It still allows everything other than what I have already "untrusted". So, I guess that might be what you would say is it's stuck on allowing scripts globally.

Re: return protection to maximum

Posted: Sun Aug 14, 2016 8:55 pm
by swj
Also, I tried most of the steps in the general troubleshooter on one of the sticky threads here. I ran a couple of different adware/malware scans with nothing detected. I don't have any of the buggy extensions. I rebuilt the extension files. I haven't added or deleted any extensions recently, and all of the ones I use were playing nicely together before, so there's no reason to suspect an extension conflict. The only things I haven't tried are resetting Noscript and the Standard Diagnostic, both of which I am hoping to avoid.

Re: return protection to maximum

Posted: Sun Aug 14, 2016 9:01 pm
by therube
The icon, does it show the S with the ! (exclamation point), S! ?

See if you haven't set Cascade.
Options | Advanced -> Trusted => Cascade

Re: return protection to maximum

Posted: Sun Aug 14, 2016 9:08 pm
by swj
@therube Unchecking the Cascade option seems to have restored it to it's previous behavior. Thank you so much for your help and for sharing your knowledge! :)