Re: port specification

mail -s "Re: [Nessus-devel] port specification" -c [email protected] [email protected]

> > nessus will accept default, or a list of ports, but will not accept
> > something like "default,1234,2345"

> This make the parsing of the port list more complex and is not very
> useful, IMHO.

It seems like straightforward preprocessing string substitution, replace
"default" with "1-1024,blah,blah,blah" but I guess if you don't think it's
useful...

> > So I run the scan, and even though 80 is the only port in the list,
> > and assume other ports closed, 80 doesn't even show up in the
> > results,

> It must have been missed by the port scan.

That is exactly the strange part I'm talking about... With nessus set to only
scan port 80 (with nmap, doesn't seem to happen with SYN scan selected
instead) and assume other ports closed, how could the following sequence
occur THREE TIMES for me:

manually check web server, it's running
nessus scan
manually check web server, still running
port 80 doesn't even show up in report, as if port scanner didn't see it.
uncheck "assume other ports closed", press start button again.
nessus scan runs again
manually check web server, still running
port 80 shows up in report this time

I wonder, are there any debugging options that would allow me to easily see
what is going to and from nmap?

Thanks

PS Nmap options are straightforward, SYN scan, Don't randomize, Aggressive.
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel