On Thu, 2003-10-09 at 09:40, Not Available wrote: > Not sure 100%, but I think that "port range" settings are only for NMap... > so, if you're running tcp connect scan instead, it's normal it will scan all > ports instead of the range you specified... try changing settings to use > NMap instead of tcp connect scan... they're separate plugins, I had them > both selected for several scans and it slowed down my job a lot! >
Tried it, but to no avail, since some plugins might be ignoring this(like Michel pointed and corrected on the #11320) , and scan ports anyway. I have following tcp ports open: 21/tcp open ftp 23/tcp open telnet 25/tcp open smtp 53/tcp open domain 80/tcp open http 81/tcp open hosts2-ns 110/tcp open pop-3 143/tcp open imap and the following udp ports: PORT STATE SERVICE 53/udp open domain 514/udp open syslog 1025/udp open blackjack But when I scan the server specifying only port 80, the results are: (The below text is cut from the saved report in ascii format) DETAILS + 10.168.8.87 : . List of open ports : o http (80/tcp) (Security hole found) o domain (53/udp) (Security warnings found) o general/udp (Security notes found) o general/icmp (Security hole found) o domain (53/tcp) (Security hole found) This backs up Michel's theory, and we might have a few more nasl scripts that needs to be patched. I will investigate which and return with more info. Max
