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]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: No text for security hole.

from [George A. Theall] Network Security [Permanent Link]
Subject: Re: No text for security hole.
Date: Mon, 26 Sep 2005 11:48:10 -0400 
On Sun, Sep 25, 2005 at 06:37:45PM -0400, hampton@cisco.com wrote:


I get the following:

results|my.net|hampton-mac.my.net|ssh (22/tcp)|19592|Security Hole|\n


It would be interesting to see what the session data reports about this
scan.

To find out, first identify Nessus' local state directory by running as
root on the nessusd host:

  fgrep 'localstatedir=' `which nessus-adduser`

By default, Nessus uses /usr/local/var; Fedora Core probably has a
different value.

Next, identify the file with the session data. It will be located under
the local state directory in the directory "nessus/users/$user/sessions"
(where $user refers to the Nessus user that ran the scan) and named
using the template yyyymmdd-hhmmss-data (eg, 20050926-114501-data).

Now grep the session data file for '<|> 19592 <|> SERVER'. Do you see
the full report in that?


George
-- 
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Reporting from the KB, part deux, George A. Theall
Next by Date:  Problem with fontconfig and nessus 2.2.5, Ray Pasetes
Previous by Thread:  Re: No text for security hole., Renaud Deraison
Next by Thread:  Loading the Nessus plugins...Segmentation fault PART 2, Kelly, Jim
Indexes:  [Date] [Thread] [Top] [All Lists]