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

from [George A. Theall] Network Security [Permanent Link]
Subject: Re: segmenation fault erases nessus config file
Date: Sat, 22 Jul 2006 14:58:54 -0400 
On Fri, Jul 21, 2006 at 07:24:15AM -0500, Scott Pate wrote:


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


Since you're connecting to a nessusd daemon running on the localhost,
you could switch to using nessus rather than NessusClient. The former is
intended for commandline usage.


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?


People generally use one of the third-party update-nessusrc scripts to
control from a commandline which plugins are enabled:

  http://www.tifaware.com/perl/update-nessusrc/
  http://edgeos.com/downloads/update-nessusrc.tar.gz

The first is something I wrote in Perl; the second is a Python-based
script from Edgeos. You need something like this since Nessus will
automatically enable any non-dangerous plugins (or any plugins if safe
checks are disabled) that are not explicitly disabled in a client
configuration, which means becomes an issue as you update plugins over time.

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




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  bug in sendmail_dns_map_txt_overflow.nasl, Nasl Scripts
Next by Date:  Re: Nessus crash: "Empty data string -- closing comm. channel", George A. Theall
Previous by Thread:  RE: segmenation fault erases nessus config file, Scott Pate
Next by Thread:  NessusClient creates different config files, Scott Pate
Indexes:  [Date] [Thread] [Top] [All Lists]