InformAction Forums

I'm running juniper network connect to connect to a vpn. network connect is a java applet that works fine if noscript is removed, but hangs firefox if noscript is enabled, even if java applets are allowed globally. The particular site I'm trying to connect to is in my whitelist. I'm running the latest noscript (1.9.? can-t tell as I have it removed at the moment) in firefox 3.0.7 i686 on Centos 5.2 x86_64.

Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7

It isn't a huge deal since I could browse in a virtual machine with noscript (and, from a security point of view, probably should) but it is annoying. Somebody reported this on the mozillazine board, and it either never got fixed or broke again in 1.9

rweiler wrote:Somebody reported this on the mozillazine board, and it either never got fixed or broke again in 1.9

Actually this issue has never been addressed, and won't probably until someone explains me how to reproduce.
Anyway, something you can test is:

1. Checking your JRE, possibly using latest from Sun
2. Checking if the problem happens also with NoScript disabled and AdBlock Plus or GreaseMonkey installed and enabled (test to see if it's a non-specific Content Policy Firefox bug)

I realize you may not have access to a juniper firewall to test against, and of course, I can't help out much with that which makes it tough to reproduce. I did verify that if I delete my .mozilla directory (and hence, all extensions including noscript), then network connect works as expected. If I then add only noscript (1.9.1.x) from the firefox repostitory and try again, it prints a 'waiting for host' down in the footer, and then that's it. Firefox is hung, none of the controls work, and I have to force quit. If I then remove my .mozilla directory and try again, network connect works. This is the jre I am using:

/opt/i386/jre1.6.0_12/plugin/i386/ns7/libjavaplugin_oji.so

Did you check with AdBlock Plus and/or GreaseMonkey?

greasemonkey crashes firefox sometime after the time it would appear to hang with nocript. I sent the error report to mozilla.

adblock+ behaves the same as greasemonkey.

Sorry I missed this post earlier but wanted to follow up and see if you figured out what was wrong?
I have access to a Juniper firewall and I'd be happy (within reason) to reproduce your scenario and see what's wrong in an attempt to replicate this to better diagnose. If you have resolved it, would love to know what it was and if not, please provide me exact steps and configurations and I will do my best to make replication and diagnose.

This is still an issue. Disabling NOSCRIPT via the Add Ons/Extension menu will allow things to work. If NOSCRIPT is active then firefox locks up and must be killed. Allowing scripts globally has no effect, firefox will still lock up.