Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Discrepancies regarding feeding nmap data to Nessus 3.2 beta (3.1.4)

Subject: Discrepancies regarding feeding nmap data to Nessus 3.2 beta (3.1.4)
Date: Thu, 20 Sep 2007 17:17:07 +0200
Regards,

We run Nessus 3.2 beta (3.1.4) on Linux. To avoid FW saturation we are feeding nmap results to Nessus. This works fine, except for some discrepancies regarding number of hosts scanned and the number of hosts appearing in the report. The details are as follows:

In nessusd.messages, the log entry "Targets:" correctly reports X number of hosts. These X targets are all read from a file. When the scan finishes, I can find Y "dead" hosts in the log. However, the report generated lists Z hosts as "alive and responding", and Z < X-Y. How can this be ?

Knut Hellebø


***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>