Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I realized, that NIS 2009's Phishing protection wasn't working, while I surfed some known phishing sites with Firefox and NoScript-Addon.
Phishing-Protection didn't work, until I allowed the sites to run scripts, while Firefox' own Phishing protection runs well with NoScript on.
So why is this the way it is?
No, it doesn’t react at all.
Without knowing the details of which sites you are testing or exactly what is going on in your machine, I will say it is possible to see this behavior.
In some cases Norton Antiphishing may need to observe the content loaded into the phishing sites by the scripts before it will flag it as suspicious.
These cases are different from when a site is on a list of known phishing sites (known to Symantec that is), where it will be blocked immediately when you try to navigate to it.
So if noscript is preventing those scripts from bringing in the content to the page, Norton Antiphishing might not see anything wrong with the page.
Matt Powers
Symantec Corp.
I used NoScript and don’t see this problem. It can take NIS 2009’s phishing protection a few seconds to detect a page, while the built-in one is immediate. Maybe that’s what you are seeing?