|
|
Home
|
Open Vulnerability Assessment System |
|
|
|
Friday, 19 December 2008 |
|
Page 2 of 3
Step 3: Prepare OpenVAS for the first run
After installing OpenVAS-Server some additional steps are needed to get your OpenVAS installation up and running. For security reasons, communication between the OpenVAS server and client is only possible through SSL encrypted connections. In order to establish an SSL encrypted connection, the server needs to have an SSL certificate. We’ll use the command openvas-mkcert to generate it. In addition, a client needs to have a user account on the server. The OpenVASServer package provides the openvas-adduser script to simplify the creation of user accounts. You are able to restricted user access rights by implementing different rule. Please read the documentation for more details.
Just open your favourite console and use the following commands as root. If you have problems to run it, please make sure to configure the PATH and library settings like mentioned in step 2. See the screenshots below:
openvas-mkcert openvas-adduser
Step 4: Performing a synchronization with a OpenVAS NVT Feed
The OpenVAS project offers a public feed of Network Vulnerability Tests (NVTs). The feed contains all NASL plugins available in the OpenVAS source code repository and now contains more than 6000 plugins. The feed is usually updated every weekday.
http://www.openvas.org/nvt-feeds.html
The following command will connect to the currently only available NVT feed. At the end, it will verify the md5 checksums of all synchronized files. If any of them fails, an error is reported. In this case you should retry a couple of minutes later:
openvas-nvt-sync
Start the sever using the following command: openvasd -D
|
|
Who's Online
We have 35 guests online
Virus Info Feed
Alexa Traffic Stats
|