On Thu, 9 Jan 2003, Aldrich, Timothy M wrote: > Now, the fact that port 2998 disappeared doesn't really bother me, in > fact I think it is a GOOD thing that nessus could kill it. What > bothers me is that no where in the report out of nessus did this port > number appear! I had nessus configured using the GUI for port range > "Default range (nmap-services + privileged ports)" and port 2998 does > appear in the nmap-services file.
Some braindead servers can crash when they are scanned. I saw it multiple times on Linux 2.0 where SYN scan was userland-visible (accept() returned, sometimes with an error). Has Nessus reported the port as open? Has check_ports.nasl finished without being killed? Is the crash reproducible? --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation." - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
