Hi
there,
I've been trying to
integrate Nessus (v 2.0) into some scripts I'm working on, and have been using
the following syntax to create a report I can then parse with my
scripts:
nessus -x -T nbe -q
localhost 1241 login pw targets output
The problem appears
to be that "output" doesn't get written to until the entire run is finished..
which, if its a large network, it can take quite some time. Is there
any way to get nessus to flush to the report file on the fly, so I can monitor
its progress? Or better yet, is the client-server protocol documented
anywhere, so I could create my own (very simple) nessus-llike client and monitor
it directly? I ask because I noticed that if I use the X front end it does
keep track of status in near-realtime, so I'm guessing the actual client-server
interface is realtime. Thanks,
Lucas.
