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]

Re: Command Line and GUI Differences

Subject: Re: Command Line and GUI Differences
Date: Tue, 14 Dec 2004 19:47:47 -0500
By looking at the process listing as soon as I start the scan (ps -ef
| grep nessusd) and then also in the nessusd.messages file.

Thanks,

Keys


On Tue, 14 Dec 2004 16:56:08 -0700, Erik Stephens <erik@edgeos.com> wrote:
On Dec 14, 2004, at 4:27 PM, Off to Oz wrote:

I can see them at the end in the original e-mail in my Gmail browser,
but not in my Outlook. However, I have included them again here.

Maybe the mail list software truncated it.  I'm stumped.  You have
ping_host.nasl (10180) and synscan.nes (11219) enabled in the config
you sent in the last email.  The following lines look right for what
you're trying to do:

 Ping the remote host[entry]:TCP ping destination port(s) : = default
 Ping the remote host[checkbox]:Do a TCP ping = yes
 Ping the remote host[checkbox]:Do an ICMP ping = yes
 Ping the remote host[entry]:Number of retries (ICMP) : = 10
 Ping the remote host[checkbox]:Make the dead hosts appear in the
report = no
 Ping the remote host[checkbox]:Log live hosts in the report = no

There is a weird line in the SERVER PREFS section: ping_hosts = no.  To
be honest, I don't know what that controls.  My guess is that it's
cruft that doesn't affect anything anymore.

How are you verifying that ping_host.nasl and synscan.nes are not
starting?  By looking at the nessusd.messages file I assume?


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

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>