Ron,
Thanks. I used to use the v1.0.2 client to drive ad-hoc scans and also
to create nessusrc config files for use when command line scanning. Now,
client v1.0.2 is considered "older". I normally upgrade things to keep
them compatible and up-to-date with the latest improvement therefore
assume I should be moving to the latest client (bearing in mind it is
still a beta). Having done that, I cannot create nessusrc files using
the 3.0.0.beta2 client. I know details of the nessusrc format are
available and also vaguely recall people mentioning 3rd-party nessusrc
editing tools. I really want to reduce working on nessusrc files with a
text editor to the minimum since they can be over 15K lines long.
Switching all the plugins on or off in the nessusrc file, for example,
would be a massive job without help from a GUI tool. Is there a
supported tool for creating and editing nessusrc files?
--
Carl Nelson
Distributed Systems Services, Computer Centre, University of Leicester,
Leicester, LE1 7RH, U.K.
Tel: +44 (0)116 252 2060, Fax: +44 (0)116 252 5027
-----Original Message-----
From: Ron Gula [mailto:rgula@tenablesecurity.com]
Sent: 20 July 2007 16:29
To: Nelson, C.M.
Cc: nessus@list.nessus.org
Subject: Re: Command Line Nessus
If you install the new Nessus Client BETA it should not
overwrite the command line 'nessus' client.
mothra:/home/rgula# md5sum /opt/nessus/bin/nessus
a054ec2c62797a142d6d39439e7ebed7 /opt/nessus/bin/nessus
mothra:/home/rgula# dpkg -i NessusClient-3.0.0.beta2-debian3_i386.deb
(Reading database ... 54667 files and directories currently
installed.) Preparing to replace nessusclient 3.0.0.beta2 (using
NessusClient-3.0.0.beta2-debian3_i386.deb) ...
Unpacking replacement nessusclient ...
Setting up nessusclient (3.0.0.beta2) ...
mothra:/home/rgula# md5sum /opt/nessus/bin/nessus
a054ec2c62797a142d6d39439e7ebed7 /opt/nessus/bin/nessus
Notice the 'nessus' client still has the same MD5 checksum
and hasn't been overwritten.
Right now, we don't have any plans to dramatically change the
configuration files used to drive the command line 'nessus' client.
Ron Gula
Tenable Network Security
Nelson, C.M. wrote:
I have a couple of queries mainly for Tenable:
I have upgraded Nessus server to v3.0.6 (from Debian). The package
includes a command line client /opt/nessus/bin/nessus. This program
takes arguments including path to an "rc" file, targets file and
specification for an output file in NBE format. This is good for me
because it is exactly what I am heavily geared-up to use. I am a
little concerned however as a consequence of finding that the new
Linux and Windows Nessus clients seem to use XML
configuration files only.
Questions:
i) Will the command line version of Nessus continue to be
offered in
the foreseeable future?
ii) If so will it use rc, XML configuration or both?
iii) If it does not support XML configuration how will it
be possible
to prepare the necessary configuration file?
I was using the older client to help create the rc file for use in
command line scanning (not slick but it worked). Now that I have
installed the latest client, which has removed the old client, I
cannot easily create and customise a suitable old style rc file
because the latest clients uses XML. Should I re-install the old
client and stop worrying because everything will work out O.K.?
--
Carl Nelson
Distributed Systems Services, Computer Centre, University of
Leicester, Leicester, LE1 7RH, U.K.
Tel: +44 (0)116 252 2060, Fax: +44 (0)116 252 5027
_______________________________________________
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
