Dear Mime,
Here is the results. So what I did is that via the lazykali script update the kali first then I updated openvas. Why does the kaliupdate takes few hours ? So what is your guide from here? After the update I am running the openvas and again stuck at the nmap.
Code:
ps ax | grep openvas
31274 ? Ss 0:00 openvassd: waiting for incoming connections
31282 pts/0 S+ 0:00 openvasmd -p 9390 -a 127.0.0.1
31284 pts/0 S+ 0:00 openvasad -a 127.0.0.1 -p 9393
31325 ? Ss 0:08 openvassd: serving 127.0.0.1
31326 pts/0 S+ 0:03 openvasmd -p 9390 -a 127.0.0.1
31340 ? S 0:00 openvassd: testing **************
31521 ? S 0:00 openvassd: testing ********* (/var/lib/openvas/plugins/nmap.nasl)
31792 pts/2 S+ 0:00 grep openvas
Code:
./openvas-check-setup.sh -v5
openvas-check-setup 2.2.3
Test completeness and readiness of OpenVAS-6
(add '--v4', '--v5' or '--v7'
if you want to check for another OpenVAS version)
Please report us any non-detected problems and
help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner ...
ERROR: OpenVAS Scanner too old or too new: 3.3.1
FIX: Please install OpenVAS Scanner 3.4.
ERROR: Your OpenVAS-6 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
root@kali:~/Desktop/lazykali# ./openvas-check-setup.sh --v5
openvas-check-setup 2.2.3
Test completeness and readiness of OpenVAS-5
Please report us any non-detected problems and
help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.
Use the parameter --server to skip checks for client tools
like GSD and OpenVAS-CLI.
Step 1: Checking OpenVAS Scanner ...
OK: OpenVAS Scanner is present in version 3.3.1.
OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 32480 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html).
OK: The NVT cache in /var/cache/openvas contains 32480 files for 32480 NVTs.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 3.0.4.
OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem.
OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
OK: OpenVAS Manager database is at revision 56.
OK: OpenVAS Manager expects database at revision 56.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 32480 NVTs.
ERROR: No OpenVAS SCAP database found. (Tried: /var/lib/openvas/scap-data/scap.db)
FIX: Run a SCAP synchronization script like openvas-scapdata-sync or greenbone-scapdata-sync.
ERROR: Your OpenVAS-5 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.