inetd services sometimes fail when scans are run against systems running Solaris 2.8. This occurs in less than 10% of systems/scans. The service that fails most often is telnetd but al least one other (local application) service has failed. Existing telnet sessions are not affected but new sessions cannot be opened until inetd is restarted, or, sometimes, when inetd recovers (by itself).

My nessusrc file is configured with (Plugins tab) 'Enable all but dangerous plugins' option and (Scan options tab) 'Port range' set to 1-15000. The configuration is otherwise the default config that you get when you first turn up Nessus. Nessus is 2.0.10 for Linux running on Fedora Core 2.

Has anyone seen this kind of behavior using Nessus against Solaris systems?

-- Mike


_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to