Closed certifiedg33k closed 9 years ago
Okay. I just found reference to OpenVAS6 scan option which uses the omp client. I will provide feedback if it is working.
That would be great.
Okay Im lost here as I dont know where to look/create an OpenVAS policy
Starting scan 'openvas' from workspace 'Test' Sending notifications for scan start... 0 notification(s) sent cmd: /opt/seccubus/scanners/OpenVAS6/scan --workspace 'Test' --scan 'openvas' -s 127.0.0.1 -u cwgueco --pw xxxxx --policy "OpenVAS Default" --targetip 10.67.157.17 -v timestamp : 20150419113117 config : HASH(0x1dad098) attach_file : perl -I/opt/seccubus/SeccubusV2 /opt/seccubus/bin/attach_file scan : openvas workspace : Test Could not find policy id for policy OpenVAS Default at /opt/seccubus/scanners/OpenVAS6/scan line 168. Sending notifications for scan end... 0 notification(s) sent cmd: /opt/seccubus/scanners/OpenVAS6/scan --workspace 'Test' --scan 'openvas' -s 127.0.0.1 -u cwgueco --pw xxxx --policy "OpenVAS Default" --targetip 10.67.157.17 -v timestamp : 20150419113117 config : HASH(0x1dad098) attach_file : perl -I/opt/seccubus/SeccubusV2 /opt/seccubus/bin/attach_file scan : openvas workspace : Test
any ideas?
Hello Christian,
Could you please display available policies names and id on your OpenVAS8 server using this command line :
omp -u
Regards,
Fabien
Le 19/04/2015 09:37, Christian Wendell C. Gueco a écrit :
Okay Im lost here as I dont know where to look/create a OpenVAS policy
bin/do-scan -w Test -s openvas -v
Starting scan 'openvas' from workspace 'Test' Sending notifications for scan start... 0 notification(s) sent cmd: /opt/seccubus/scanners/OpenVAS6/scan --workspace 'Test' --scan 'openvas' -s 127.0.0.1 -u cwgueco --pw xxxxx --policy "OpenVAS Default" --targetip 10.67.157.17 -v timestamp : 20150419113117 config : HASH(0x1dad098) attach_file : perl -I/opt/seccubus/SeccubusV2 /opt/seccubus/bin/attach_file scan : openvas workspace : Test Could not find policy id for policy OpenVAS Default at /opt/seccubus/scanners/OpenVAS6/scan line 168. Sending notifications for scan end... 0 notification(s) sent cmd: /opt/seccubus/scanners/OpenVAS6/scan --workspace 'Test' --scan 'openvas' -s 127.0.0.1 -u cwgueco --pw xxxx --policy "OpenVAS Default" --targetip 10.67.157.17 -v timestamp : 20150419113117 config : HASH(0x1dad098) attach_file : perl -I/opt/seccubus/SeccubusV2 /opt/seccubus/bin/attach_file scan : openvas workspace : Test
Done
any ideas?
— Reply to this email directly or view it on GitHub https://github.com/schubergphilis/Seccubus_v2/issues/192#issuecomment-94248286.
Hello,
Below is the information requested:
WARNING: Verbose mode may reveal passwords!
Will try to connect to host 127.0.0.1, port 9390... 8715c877-47a0-438d-98a3-27c7a6ab2196 Discovery 085569ce-73ed-11df-83c3-002264764cea empty daba56c8-73ec-11df-a475-002264764cea Full and fast 698f691e-7489-11df-9d8c-002264764cea Full and fast ultimate 708f25c4-7489-11df-8094-002264764cea Full and very deep 74db13d6-7489-11df-91b9-002264764cea Full and very deep ultimate 2d3f051c-55ba-11e3-bf43-406186ea4fc5 Host Discovery bbca7412-a950-11e3-9109-406186ea4fc5 System Discovery Command completed successfully. !--- then with this I used "Discovery" as a policy and then I get some very long output. see http://pastebin.com/EFzgCmWj.
From the Seccubus Web, it has the IVIL output in the Runs Tab but no results in the Findings TAB. Missing something?
Thanks!
Would it be possible to anonymise the IVIL file and share it with us?
Hello,
I opened the IVIL XML output and it only has this: !-- <?xml version="1.0" standalone='yes'?>
!-- Did I run the do-scan properly? or my settings wrong? Below are my parameters for the openvas scan: -s 127.0.0.1 -u cwgueco --pw $PASSWORD --policy 'Discovery' --targetip $HOSTS
Should I use another policy?
Christian,
According to the log file you provided, It looks like the OpenVAS scan do not really start. I am not 100% sure of the reason, I see two possible issues :
Regards,
Fabien
Le 20/04/2015 15:06, Christian Wendell C. Gueco a écrit :
Hello,
I opened the IVIL XML output and it only has this:
<?xml version="1.0" standalone='yes'?>
OpenVAS6 20150420162736
Did I run the do-scan properly? or my settings wrong? Below are my parameters for the openvas scan: -s 127.0.0.1 -u cwgueco --pw $PASSWORD --policy 'Discovery' --targetip $HOSTS
Should I use another policy?
— Reply to this email directly or view it on GitHub https://github.com/schubergphilis/Seccubus_v2/issues/192#issuecomment-94446862.
FIrst thing we need to establish is what happens when you run the do-scan can you add '-v -v -v' to the do-scan command?
Thanks for the suggestions. I will get back on this as the dev server with secubbus is acting funny as I initiated the do-scan with -v -v -v and it finished but on the backend I see openvassd processes still running targeting the target IP.
Cleaning up, not touched for a long time
Hello,
I have just managed to install Seccubus (via seccubus_2.14.B262_all.deb package) onto a Debian VM (7.8). It has OpenVAS 8.0.1. installed within the same system. I cannot find any reference on OpenVAS for it command line client except the openvas-cli. Is this correct?
Regards,