slackbuilds_ponce/network/openvas-client
David Somero aabe868f65 network/openvas-client: Misc automated cleanups.
Signed-off-by: David Somero <xgizzmo@slackbuilds.org>
2010-06-04 01:13:39 -04:00
..
doinst.sh network/openvas-client: Updated for version 3.0.0 2010-05-13 00:37:44 +02:00
openvas-client.info network: nitpicks on ordering of .info files 2010-05-18 00:29:17 -05:00
openvas-client.SlackBuild network/openvas-client: Misc automated cleanups. 2010-06-04 01:13:39 -04:00
README network/openvas-client: Updated for version 3.0.0 2010-05-13 00:37:44 +02:00
slack-desc network/openvas-client: Added to 12.2 repository 2010-05-12 23:32:37 +02:00

OpenVAS stands for Open Vulnerability Assessment System and is a network
security scanner with associated tools like a graphical user front-end. The
core component is a server with a set of network vulnerability tests (NVTs)
to detect security problems in remote systems and applications.

OpenVAS products are Free Software under GNU GPL and a fork of Nessus.

This package provides the OpenVAS scanner. To build a complete OpenVAS scanner
installation, however, you have to compile and install the packages in the
following sequence:
 1. openvas-libraries
 2. openvas-scanner
 3. openvas-client

The openvas-client GUI is needed to interact with the OpenVAS scanner, however
there are some new optional modules:
 1. openvas-scanner for storing and organizing scans on a central server in a
 SQL database
 2. openvas-administrator for User-, Feed- and Settings-Management
 3. greenbone-security-assistant for a web-based Vulnerability Management

This package provides the OpenVAS client. You need GTK libraries and
OpenSSL are highly recommended, both of them are avalaible from Slackware.

As a last note, keep in mind that this is a major version transition: the
older openvas-libnasl and openvas-plugins packages no longer exists,
openvas-server has been replaced by the openvas-scanner package and there are
the new optional modules. A straight upgradepkg (with removal of deprecated
packages) *SHOULD* work but also consider to backup your old configuration and
starting over from a fresh OpenVAS installation.