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: segmenation fault erases nessus config file

Subject: RE: segmenation fault erases nessus config file
Date: Fri, 21 Jul 2006 07:24:15 -0500
 

-----Original Message-----
From: nessus-bounces@list.nessus.org
[mailto:nessus-bounces@list.nessus.org] On Behalf Of George A. Theall
Sent: Thursday, July 20, 2006 8:57 PM
To: Nessus@list.nessus.org
Subject: Re: segmenation fault erases nessus config file


I can reproduce this with  the latest, 1.0.0.RC4. [Btw, "NessusClient
-h" gives a more complete version number.] I also get a Segfault when I
run something like "NessusClient -c ~/.nessusrc -qP localhost 1241
theall nopass". That >>looks much like what was reported here:

 http://mail.nessus.org/pipermail/nessus/2006-January/msg00030.html

But that was reportedly fixed in 1.0.0.RC3.


Indeed I am running 1.0.0.RC4.  

[root@localhost ~]# NessusClient -h
NessusClient, version 1.0.0.RC4

I read the posts, but didn't see a solution.  Is there a workaround for
editing the nessusrc file by hand?




The unix client config files are re-written in the course of each scan.
Apparently, the segfault you're experiencing occurs while this is
happening.

If the config files are indeed re-written for each scan, what would you
recommend is the correct way to run nessus in batch mode so I can edit
the config file and have my changes persist across scans?



Scott
_______________________________________________
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>