Google toolbar vs noscript problem

[alexo]

Unfortunately, it seems that Google decided to document the workaround instead of fixing the issue.

If you disapprove, I suggest you add your voice here.

[Guest]

That tip doesn't work/

[KEP]

However there's a work-around: just open NoScript Options|Whitelist and add file://.

Nope, doesn't work here. I already had "file://" whitelisted, and added "file:" just to be redundant. No good. List still doesn't drop.

Running Google Toolbar v6.1.20091119W and NoScript v1.9.9.35

Any news on this front? I'm surprised this thread died out.

Thanks!

[Fred]

Hello,

@KEP » Sun Jan 10, 2010 6:15 pm

Google Toolbar Version 6.1.20091216W = ok.

http://toolbar.google.com/

thanks for NoScript!

[which_doobie_you_be]

This has worked for me in the past, but I wonder what the ramifications of adding 'file://' to the whitelist are? Could this very general-looking entry open up your browser to exploits?

[Giorgio Maone]

This has worked for me in the past, but I wonder what the ramifications of adding 'file://' to the whitelist are? Could this very general-looking entry open up your browser to exploits?

Adding file:// just allows HTML files you open from your own local filesystem to run JavaScript.
Yes, it widens the attack surface, but it would be quite a difficult attack against a security-conscious user because it requires you to save a HTML file locally, then browsing the container directory and double click it.

[Alison]

I'm having this same problem now after not having it for quite some time. I'm running the latest NoScript, 2.1.0.3, Google toolbar Version 7.1.20110316W and FF 4.0.1. The Google Toolbar history was working, but is no longer. If I select to have it replace FFes, then that history does not work. If I select to put the searchbox in the Google toolbar, then that history does not work.

I've added file:// to the NoScript whitelist, uninstalled and reinstalled the toolbar and noscript and I've reset Noscript to defaults. None of those fixed the issue.

What else can folks suggest I try.

- Alison

[Alison]

I've solved the issue by installing 2.1.0.4rc11. So something in that version fixed the issue.

Thank you for NoScript!!!

- Alison