Installing OpenVAS 9 from the sources

In last month Greenbone Networks and OpenVAS development team have finally presented new OpenVAS 9 with new GUI, improved multi-scanner support, improved asset management, etc. We have been waiting for this release for 2 years!

Upd. Please note, that entire procedure for separating scanners onto separate hardware/distributed hardware in different datacenters has changed completely – and that it’s a good idea to get familiar with this new procedure prior to upgrading to OpenVAS 9. 😉

When Debian installation was finished, I, for some reason, had the same connection active used for two network interfaces (NAT and host only), and only one interface, NAT, really worked. With nmtui I made one more connection and for each connection I set particular interfaces: eth0 for one, eth1 for another. I also set static ip address 192.168.56.120 for the host.

ssh vmuser@192.168.56.120.
su -

Warning! When elevating privileges, use `su -` to avoid problems with the locale.

19 thoughts on “Installing OpenVAS 9 from the sources”

It might be worth mentioning somewhere in the post that the entire procedure for separating scanners onto separate hardware/distributed hardware in different datacenters has changed completely – and that it’s a good idea to get familiar with this new procedure prior to upgrading to OpenVAS 9. 🙂

root@OpenVas9:~# chmod +x openvas_commander.sh
root@OpenVas9:~# clear
root@OpenVas9:~# ./openvas_commander.sh –install-dependencies
./openvas_commander.sh: line 19: curl: command not found
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package pkg-config is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libpopt-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package rpm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package curl is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libglib2.0-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libglib2.0-0

Package libpcre3-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package python-setuptools is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package gnutls-bin is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libsnmp-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libsnmp-base

actually i have the install rolling now on debian-8.7.1-amd64-netinst
I installed curl_7.38.0-4+deb8u5_amd64.deb but ran your script again and then noticed that there was a need for an apt-get -f install to add another dependencie libcurl

Currently, the openvas manager and the openvas scanner are listening on a unix socket. I didn’t find any conf files enabling me to change this behaviour. Is it possible to listen on a TCP socket (9390 for example) ?

Greetings!
Maybe you can help me with Windows Failed Authentication (credentialed scans)
On OpenVAS 6 the credentialed scans worked very well but now it appears like there are some error with SMB protocol when the scanner tryes to authenticate. We patched the targets with ms17-010 and dont know if thats the problem.

There are no enough information on OpenVAS offcial page and mabe yuo have some hints about this problem.

I have a problem with this, when I run ./openvas_commander.sh –show-releases the script doesn’t return response. The dependencies it’s correctly installed. I don’t know why? Can you help me? (I’m sorry for my bad English)

Meta

This is my personal blog. The opinions expressed here are my own and not of my employer. All product names, logos, and brands are property of their respective owners. All company, product and service names used here for identification purposes only. Use of these names, logos, and brands does not imply endorsement. You can freely use materials of this site, but it would be nice if you place a link on https://avleonov.com and send message about it at me@avleonov.com or contact me any other way.