This page has been nominated for deletion.
The given reason is: This page should be deleted because the OpenVAS project name has been renamed in GVM and old OpenVAS loader package with all components removed from gentoo tree. GVM is a major update and all the commands and informations on this page are deprecated. We have new wiki page for new GVM --> Greenbone_Vulnerability_Management
If you disagree with its deletion, do not remove this notice; discuss your objections on the associated discussion page.
Administrators, please remember to check if anything links here and the page history before deleting.This notice should remain for a minimum of 1 month after it was placed on the page. If discussion is still ongoing it should remain until a consensus is reached, at which time the page may be deleted or this notice may be removed. (However, if the page has only been edited by the user who nominated it for deletion and/or is in the nominator's user space, then a speedy deletion may be called for.)
The following steps can be checked at any point by running the openvas-check-setup utility.
Generate an SSL certificate
Before OpenVAS can be started, an SSL certificate must be generated:
Generate the client's SSL certificate
openvas-mkcert-client -n -i
Download vulnerability list
Download the vulnerability list with the following command:
Update the scan daemon's cache
Rebuild the management daemon's NVT cache
Download the SCAP data
Download the OpenVAS CERT database
Create a user
Users will not be able to login until accounts have been created for them. Pretending a user by the name of Larry would like to create an account:
openvasmd --create-user larry
Unless you want a large GUID for a password, be sure to change it:
openvasmd --user=larry --new-password=SuPErSeCR3TP@assw0rd
Users can be listed with the following command:
Stuck on configuration steps
Service not starting
Check the log files located at /var/log/openvas/.