RE: command-line usage

Fri, 24 Feb 2006 14:29:58 -0800

I see.
But the nessusrc file already contains the target, so I guess the 'targetsfile' is some that is redundant, but needed...
 
Does that sound right?
 
Thanks!!

From: sawall [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 4:27 PM
To: Mark Feferman
Cc: [email protected]
Subject: Re: command-line usage

here's the command i usually use:

nessus -c nessusrc -x -q localhost 1241 nessususer nessuspwd -T nbe targetsfile outputfile.nbe

looks like your missing your targetsfile.  the file with list of hosts to scan.

chris


On 2/24/06, Mark Feferman <[EMAIL PROTECTED]> wrote:
According to the -h option, I have to specify the -q (batch option).  The format below must be missing some stuff...
I still can't get the darn thing to work properly.
 
This is what the '-h' option says:
 
nessus, version 3.0.1.
 
Common options :
 nessus [-vnh] [-c .rcfile] [-V] [-T <format>]
Batch-mode scan:
 nessus -q [-pPS] <host> <port> <user> <pass> <targets-file> <result-file>
List sessions  :
 nessus -s -q <host> <port> <user> <pass>
Restore session:
 nessus -R <sessionid> -q <host> <port> <user> <pass> <result-file>
Report conversion :
 nessus -i in.[nsr|nbe] -o out.[xml|nsr|nbe|html|txt]
 
General options :
        -v : shows version number
        -h : shows this help
        -n : No pixmaps
        -T : Output format: 'nbe', 'nsr', 'html', 'xml' or 'txt'
        -V : make the batch mode display status messages
            to the screen.
        -x : override SSL "paranoia" question preventing nessus from
            checking certificates.
 
The batch mode (-q) arguments are :
        host     : nessusd host
        port     : nessusd host port
        user     : user name
        pass     : password
        targets  : file containing the list of targets
        result   : name of the file where
                   nessus will store the results
        -p       : obtain list of plugins installed on the server.
        -P       : obtain list of server and plugin preferences.
        -S       : issue SQL output for -p and -P (experimental).
        -l       : Display license information
 
 
According to the PDF documentation, you have to use Batch-mode for command-line stuff, so I've tried the following:
 
nessus -q -p <host> 1241 <user> <pass> -c /tools/nessus/mynessusrc /tools/nessus/output/scan.nbe -T nbe
 
This doesn't work.
 
Any other thoughts?
 
Thanks in advance,
Mark
 

From: sawall [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 24, 2006 12:49 PM
To: Mark Feferman
Cc: [email protected]
Subject: Re: command-line usage

You can use the -c option to specify the rc file.

nessus [-vnh] [-c .rcfile] [-V] [-T <format>]

Chris



On 2/24/06, Mark Feferman <[EMAIL PROTECTED]> wrote:
Hi,
I'm having the hardest time with the command-line usage.  I have the latest version installed (3.0.1) and have used the GUI client (it's really nice). 
 
I'm trying to setup some CRON jobs for regular scanning but can't seem to get the command-line format to run Nessus correctly.  In the GUI, I have created a task and a scope.  Below my home directory, I see the following path and file:
 
~/.nessus/Monthly_Scans/External_Scope/nessusrc
 
I would like to be able to use that file's settings for the scan that I launch in the cron job.
 
Any help would be greatly appreciated.
 
Thanks in advance,
Mark
 
 
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus



_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to