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. |

| Subject: | Re: Command Line and GUI Differences |
|---|---|
| Date: | Tue, 14 Dec 2004 16:22:43 -0700 |
On Dec 14, 2004, at 3:23 PM, Off to Oz wrote:
I use the .nessusrc file from the above scan and run a scan using the command line client and now nessus does not run the ping_host.nasl or even the synscan.nes. It just goes out full-blown with a bunch of plugins on all the hosts. It does not seem to care if they're alive or not.
Can someone please explain why? I have pasted the nessusd.conf and nessusrc files here with this mail.
Best regards, Erik Stephens www.edgeos.com Managed Vulnerability Assessment Services
_______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | unscanned_closed not always working?, Jason Haar |
|---|---|
| Next by Date: | Error compiling nessus-core, John Madden |
| Previous by Thread: | Command Line and GUI Differences, Off to Oz |
| Next by Thread: | Re: Command Line and GUI Differences, Off to Oz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |