OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: JavaScript port scanning

From: pdp (architect) (pdp.gnucitizengooglemail.com)
Date: Wed Aug 02 2006 - 07:41:07 CDT


At the top of the web page I am mentioning that the scanning process
is not accurate... that's it, finito. you might get better results by
increasing the timeout value... give it something like 10000 or even
more. Still, it might not work! Take some time and go through the tiny
js file to see how it works.

BTW, you might have better luck with IE6.

cheers

On 8/2/06, TheGesus <thegesusgmail.com> wrote:
> I tried this out on my test network (firefox, no proxy) and it
> reported closed ports as being open, even silly ports like -1 and
> 77777.
>
> Am I missing something?
>
> BTW, I could not find an M to RTFM.
>
> On 8/1/06, pdp (architect) <pdp.gnucitizengooglemail.com> wrote:
> > Inspired by SPI Dynamics - tiny JavaScript port scanner
> > http://www.gnucitizen.org/projects/javascript-port-scanner/
> >
> > --
> > pdp (architect)
> > http://www.gnucitizen.org
> >
>

--
pdp (architect)
http://www.gnucitizen.org

-------------------------------------------------------------------------
Sponsored by: Watchfire

Do you test web applications for XSS, SQL Injections, Buffer Overflows,
Logical issues and other web application security threats? Why not
automate this work with Watchfire's AppScan, the world's leading
automated web application scanner. Download AppScan today!

https://www.watchfire.com/securearea/appscancamp.aspx?id=701300000008BP9
--------------------------------------------------------------------------