On Jun 24, 2008, at 4:14 AM, Roman Medina-Heigl Hernandez wrote:
Another Windows issue (I guess): If I create a new policy, and enter
"credentials", the window gets screw (same text is duplicated upper
and
down, using "half" a font :)).
I don't seem to be able to replicate this using the client included
with Nessus Windows 3.2.1. Would you mind upgrading to that and seeing
if it resolves the issue? If not, send me a screenshot along with some
more details about how to reproduce the issue and I'll forward it to
the developers.
1.- If I check the three marks (icmp, tcp, arp), I suppose the host
will
only be detected as dead when the three tests fail, am I right?
No, if either test fails, the host will be marked as dead.
2.- When a host is detected as dead, is it right to assume that all
modules
(ping_host.nasl, dont_scan_printers.nasl, etc) got a failure? In other
words, the host is alive when at least one of the modules thinks so
(some
kind of "OR" logical operation), and it is dead when all modules fail
(logical "AND"). Right?
No, marking a host as dead prevents Nessus from launching further
plugins against it.
No, it's a LAN connection (ADSL). Btw, is there any doc discussing
Windows
vs Linux version differences such as the former one?
I don't think so, but I'm not sure.
The PPP / PPTP interface issue is mentioned in the 3.2 Installation
Guide (look for it at http://www.nessus.org/documentation/), as is the
inability to do a TCP Connect scan using Nessus Windows (because of
limitations in the Windows TCP/IP stack).
George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
