On Fri, Jul 07, 2006 at 12:05:37PM -0500, Morris, Joshua wrote: > I see the command line worked very well with older versions of Nessus, > however, it doesn’t seem to work as well with version 3. I am trying to > automate my scans but the “nessuscmd” does not have many options as far > as report specification and output.
There has never been something called "nessuscmd" in any of the distributions of Nessus that I've used. Are you sure this isn't a home-grown script? If so, have you accounted for the possibility that the client has been installed in a different location than before; ie, /opt/nessus/bin/nessus? > Right now, I have created cmd files > which contain “nessuscmd 192.168.0.1 allsafe” for the ip’s I want to > scan. This definitely looks like something home-grown. > There are no more _T and –q it seems. [EMAIL PROTECTED]> nessus -h nessus, version 3.0.2. Common options : nessus [-vnh] [-c .rcfile] [-V] [-T <format>] Batch-mode scan: nessus -q [-pPS] <host> <port> <user> <pass> <targets-file> <result-file> Report conversion : nessus -i in.[nsr|nbe] -o out.[xml|nsr|nbe|html|txt] They're still there. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
