Full Disclosure mailing list archives
Re: JavaScript port scanning
From: "pdp (architect)" <pdp.gnucitizen () googlemail com>
Date: Wed, 2 Aug 2006 13:41:07 +0100
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 <thegesus () gmail 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.gnucitizen () googlemail 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 _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Re: JavaScript port scanning TheGesus (Aug 02)
- Re: JavaScript port scanning pdp (architect) (Aug 02)
- Re: JavaScript port scanning pdp (architect) (Aug 02)
- <Possible follow-ups>
- Re: JavaScript port scanning pdp (architect) (Aug 02)