InformAction Forums

This option is UNCHECKED
NoScript Options > Apperance > Contextual menu > Allow Scripts Globally (dangerous)
This option is UNCHECKED
as are most options except the temporarily allow/revoke temporary.

yet at least once a month, somehow, magically, scripts get allowed globally (apparently through the noscript status icon )
it has happened since I started using NoScript a few years ago, but I cannot replicate it on demand
i really have no clue why it happens

Anyone seen this? Anyone know whats going on?

Thanks

What is the value of the about:config pref noscript.globalwarning. Make sure it's set to true.

Alan Baxter wrote:What is the value of the about:config pref noscript.globalwarning. Make sure it's set to true.

it was set to true

I don't know what else to suggest. I don't remember seeing your issue reported before.

Hi everybody,

I just want to support the original poster. It happened about some weeks ago where first on one, later on several of my firefox 3 (currently 3.6.13)-installations the noscript-icon in the ff-tray warned me that all scripts were allowed globally. I didn't check that option in the first place, but I wasn't sure, so I unchecked it. After a ff-restart again the option "allow scripts globally (not recommended)" was checked.

I recently decided to uninstall the noscript addon and to reinstall it from scratch - unfortunately the issue persists. I am glad to read now, that at least one other user has got a similar problem. In my case it is not only randomly, but after every launch of firefox that noscript allows all scripts.

Needless to say that also in my installation(s) the mentioned pref "noscript.globalwarning" *is* set to true.

I use firefox + noscript on Windows XP 32 & 64bit, Vista Business 32 bit and Win 7 64 bit at home and at work with different anti-virus-software. Therefore I cannot believe that a virus or some similar malware is causing the issue.

Can anybody imagine what to do to isolate the problem?
As a workaraound: Is there something like a "lock" in prefs to prevent users from checking the "allow scripts globally (not recommended)"-option?

Regards,

Thomas

HOTKEYS?
about:config
I FOUND TWO HOTKEYS FOR NOSCRIPT

noscript.keys.ui;ctrl shift S
noscript.keys.toggle;ctrl shift VK_BACK_SLASH.|

maybe the toggle function is getting confused somehow?

I would like to confirm this issue. NoScript was running fine for years(?). But today I was confused because I clicked the NS icon to see what script sources a site did use and I saw that all were allowed (except those two which were on my black list). I went to the settings and saw the checkmark in the allow scripts globally box.
I do not know that I enabled this crazy setting intentionally. Thanks for the key codes - I switched them off now - but they did not seem to toggle this anyway. Firefox 3.6.13 on openSUSE 11.1 with about 20 extensions.

Best regards

Which extensions?
Is would be not the first time an extension turns scripts on globally, on purpose or by accident.

Hm.. Extensions should be sandboxed.. or so

Firefox 3.6.13 (2010120300) Linux (x86-gcc3)

• Adblock Plus 1.3.3
• Adblock Plus Filter Uploader 2.1
• BetterPrivacy 1.48.3
• British English Dictionary 1.19.1
• Clippings 3.1.4
• ColorfulTabs 4.6.5
• Deutsches Wörterbuch 2.0.2
• Download Statusbar 0.9.7.2
• DownThemAll! 2.0.1
• Element Hiding Helper für Adblock Plus 1.1
• Extension List Dumper 1.14.8
• FAYT 2.0.5
• Firebug 1.6.2
• FireFTP 1.0.10
• Fission 1.0.9
• Flashblock 1.5.14.2
• Image Zoom 0.4.6
• Lazarus: Form Recovery 2.0.5
• Master Password Timeout 0.3.1
• Multi Links 3.0.0.14
• NoScript 2.0.9.9
• openSUSE Firefox Erweiterungen 1.0.1
• RefControl 0.8.14
• Resizeable Textarea 0.1d
• Resurrect Pages 2.0.6
• Searchbar Autosizer 1.4.7
• Tab Mix Plus 0.3.8.5
• Update Scanner 3.1.3
• User Agent Switcher 0.7.3
• YouTube to MP3 1.0.7

all only installed from https://addons.mozilla.org/de/firefox/
recently updated (according to extension dumper): multilinks (2011-03-09), clippings (2011-02-16), downThemAll (2011-02-10)

And sorry - I cannot tell the noscript version which was running because noscript was updated at the last start-up. Until now it kept the standard "forbid all except ..." setting.

Thank you for this software and support!

Hmm ... and it happenend again - enable scripts globally was switched on again today.
How to prevent it?

Best regards
munitalp

munitalp wrote:Hmm ... and it happenend again - enable scripts globally was switched on again today.
How to prevent it?

Best regards
munitalp

Grr it happened to me again today (i posted before)
now running firefox 4.0.1 with addons
BetterPrivacy 1.50
NoScript 2.1.0.3
all I was doing was switching between firefox tabs, between firefox instances, between other apps ... alt +tab, ctrl+tab
and I go back to one firefox instance and i see globall scripts are allowed

now, to prevent it, i'm guessing edit
noscript-2.1.0.3-sm+fn+fx.xpi\chrome\noscript.jar\content\noscript\Main.js
and remove

case "global":
this.globalJS = this.getPref(name, false);
break;

and replace every mention of this.globalJS with false
then edit
noscript-2.1.0.3-sm+fn+fx.xpi\chrome\noscript.jar\content\noscript\RequestWatchdog.js
and replace ns.globalJS with false
AFAIK, that should make it impossible to turn on scripts globally

Guest wrote:

munitalp wrote:Hmm ... and it happenend again - enable scripts globally was switched on again today.
How to prevent it?

Best regards
munitalp

Grr it happened to me again today (i posted before)
now running firefox 4.0.1 with addons
BetterPrivacy 1.50
NoScript 2.1.0.3
all I was doing was switching between firefox tabs, between firefox instances, between other apps ... alt +tab, ctrl+tab
and I go back to one firefox instance and i see globall scripts are allowed

now, to prevent it, i'm guessing edit
noscript-2.1.0.3-sm+fn+fx.xpi\chrome\noscript.jar\content\noscript\Main.js
and remove

case "global":
this.globalJS = this.getPref(name, false);
break;

and replace every mention of this.globalJS with false
then edit
noscript-2.1.0.3-sm+fn+fx.xpi\chrome\noscript.jar\content\noscript\RequestWatchdog.js
and replace ns.globalJS with false
AFAIK, that should make it impossible to turn on scripts globally

yay, i've tested this and it works
global script doesn't work no way no how (js no run),
but if you enable it, the buttons will change ,
but it still won't work (js no run) unless you had temporarily allowed a domain
so even if this scenario happens again, and scripts somehow mysteriously get turned on globally, they won't run

you will have to delete META-INF\* or firefox won't run it (fail sigcheck)

i can't stand lying UIs so I reinstalled the official release, if it happens again, I might look into getting the buttons to play along