Soren wrote:
maccrawj wrote:
Even if you were to fix Flash in this way, it's still blocking other
functions like scripting.
Yep, but only Cross Site Scipting exploits.
My point was removing flash blocking globally (suggestion offered I replied to) !=
whitelist the domain. Flash blocking is only one thing NoScript blocks, so it still
blocks whatever functionality it's configured to since the domain is untrusted.
Why you bring up XSS I'm not sure?
If one wants protection against scripts acting on page load and page
exit, there's no way around web washer.
Again I'm lost about where you are going with this. With a domain not whitelisted, no
scripts or other content that NoScript is configured to block will run (short of a
NoScript bug). What are you saying?
Sure sounds like he has not whitelisted the domains hosting netgear
content (there may be more than netgear.com) which is the ultimate fix.
No, and NoScript is still buggy as hell.
Eh? I've used netgear.com and have no issues, what do you mean by "no" vs. what I
have said?
I've months ago attempted a dialouge with the NoScript author, revealing
several bugs, but no luck so far. He responds to email, but plays the
ignorance card. No hope ;)
Bugs such as? Even buggy it's better than surfing naked if it blocks most otherwise
active content.
Seems like today it's all about profiling and mining data, not
supporting it.
I contacted him about an issue with wildcard domain whitelist patterns not working
and got a response within 24hrs. Of course I went through the forums not email, so YMMV.
For a quick NoScript fix you can use Ctrl+Shift+Backslash to toggle
whitelisting of current domain (netgear.com for example).
Brian Weeden wrote:
If you go into the NoScript options there is a place where you can set
exactly what it blocks, and Flash is one of them.
I leave it blocked because it kills a lot of annoying ads but you can
easily
allow Flash and still keep scripting disabled.
