On Fri, 13 Feb 2004, [iso-8859-1] a a wrote: > Nessus is working great except for the fact that a 'safe' scan seems > to hang/crash NFS on a few servers.
You know the only really safe test is no test because the basic goal of any meaningful test is to try to break things. It would be very helpful if you determined what breaks those servers (port scan? find_services? any NFS specific plugin? (*)). (*) An idea: make it possible to run plugins sequentially (yes, I can already do it when I set the maximum to 1), with delays between them (delay_between_tests does not affect plugins running against different ports, right?), and with an arbitrary liveness test between them (perhaps in the form of a user-specified NASL script). > I want to exclude the NFS port (2049 tcp & udp) from the scan I am > running. You can try excluding these ports from the set of scanned ports and enable "Consider unscanned ports as closed". You can also add an egress filtering rule preventing packets to those ports from leaving the Nessus server. Of course, the OS of the server (or some node between the server and tested hosts) must be able to filter outgoing packets. I do not think it makes any sense to modify services.txt. --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation." _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
