Bart Bailey said:
The enabling of js allows scripting exploits that wouldn't,
or rather shouldn't, otherwise be presented to the internet.
Javascript is generally disabled on my main machine, but on this one it
tends to be enabled. While it was possible I'd only ever done the Sygate
scan with js enabled, it seemed unlikely. After all, I was testing security
settings, you know? But I have now disabled it on this one - I have a web
page with an onmouseover I added (that pops up the message "You need
javascript enabled to view this!"......It's very annoying but hopefully a
As to a disparity between GRC versus Sygate, I suspect Sygate is
utilizing the js to enable some internal activity that wouldn't be
available without it. If you think some particular port is open, get a
friend to nscan you (with js disabled).
http://www.nscan.org
I'll mosey on over and check it out, but the point - the only point - is
that GRC's scan is insufficient. Regardless of whether my machine is
vulnerable where yours isn't, or vise versa. What happens is the Sygate
scan flags a few ports as Closed as opposed to Stealthed, where GRC
flags them all as Stealthed. Create a rule to then block all traffic via one
of those relevent ports and that port will now be detected as Stealthed by
Sygate too. Javascript or no.
Shane