On 2014-07-09 14:38, Johannes Schönborn wrote:
Hi there,
hi Hani,
I now did everything from scratch for arch and ubuntu, following i.e.
this guide http://hackertarget.com/install-openvas-7-ubuntu/ [1]
14682 1 0 09:12 ? 00:00:00 openvassd: Waiting for
incoming connections
14777 1 0 09:21 pts/0 00:00:00 openvasmd
Scanner runs, logs says
openvassd.messages
[Wed Jul 9 13:12:46 2014][14682] openvassd 4.0.1 started
[Wed Jul 9 13:21:38 2014][14770] Communication closed by client
[Wed Jul 9 13:21:38 2014][14770] Client not present
...
[Wed Jul 9 13:23:06 2014][14865] Failed reading client-requested
OTP version.
openvasmd.log
event task:MESSAGE:2014-07-09 13h24.30 UTC:14910: Status of task
(90aa9fdd-c133-44ea-b9a1-96358540cb52) has changed to New
event task:MESSAGE:2014-07-09 13h24.31 UTC:14910: Task
90aa9fdd-c133-44ea-b9a1-96358540cb52 has been created by cpt
event task:MESSAGE:2014-07-09 13h24.31 UTC:14910: Task
90aa9fdd-c133-44ea-b9a1-96358540cb52 could not be started by cpt
event wizard:MESSAGE:2014-07-09 13h24.31 UTC:14910: Wizard
quick_first_scan could not be run by cpthook
lib serv:WARNING:2014-07-09 13h24.31 utc:14915:
openvas_server_verify: the certificate is not trusted
lib serv:WARNING:2014-07-09 13h24.31 utc:14915:
openvas_server_verify: the certificate hasn't got a known issuer
Also, why would OpenVAS internally not trust the certificates it
generated?ls
Quick glance at the guide, he is using "openvas-mkcert" without the -f
flag, and without mentioning that you should copy the server and CA key
pairs manually in that case.
Solution:
openvas-mkcert -f
openvas-mkcert-client -i -n
restart all daemons.
Regards,
Hani.
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss