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: Holes/warnings all show Sambar text

Subject: Re: Holes/warnings all show Sambar text
Date: Mon, 23 Aug 2004 11:59:50 -0700 (PDT)
On Thu, 19 Aug 2004, George Theall theall-at-tifaware.com |nessus| wrote:

I've seen this a couple of times, and each time the problem's arisen
because I've upgraded Nessus and the cached plugin descriptions somehow
no longer agreed with the newer version. Shutting down the daemon,
removing the directory ".desc" in the plugins directory, and restarting
the daemon solved the problem.

I've cleared out all nessus files from the system a couple of times now,
just in case something like this was creating an issue.

Symptom 2 seems to result from the plugins getting SEGV aborts, which is
not the best way to handle this situation.  It looks like when the plugins
abort, the server treats this as if they completed successfully with no
security holes found-- not my choice of failure modes!  :-)  If it has to
fail, I'd rather it failed safe by listing a genericish security warning
that the plugin was unable to complete its checks.

This problem seems to be specific to the system where I'd like to run the
Nagios daemon.  A test run on a different system worked fine, so now I
just need to find out why.  I suspect that there may be some libraries or
utilities present on one that are missing on the other.

Does anyone know why when a plugin aborts, Nessus treats this as a
success?

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

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