This is the libraries module for the Greenbone Vulnerability Management Solution.

It is used for the Greenbone Security Manager appliances and provides various functionalities to support the integrated service daemons.

 All release files are signed with the Greenbone Community Feed integrity key. This gpg key can be downloaded at https://www.greenbone.net/GBCommunitySigningKey.asc and the fingerprint is 8AE4 BE42 9B60 A59B 311C 2E73 9823 FAA6 0ED1 E580.

This module can be configured, built and installed with following commands:

cmake .
make install

For detailed installation requirements and instructions, please see the file INSTALL.md.

If you are not familiar or comfortable building from source code, we recommend that you use the Greenbone Community Edition, a prepared virtual machine with a readily available setup. Information regarding the virtual machine is available at https://www.greenbone.net/en/community-edition/.

The gvm-libs module consists of the following libraries:

• base: All basic modules which require only the glib library as a dependency.

• util: All modules that require more than the glib library as dependency.

• gmp: API support for the Greenbone Management Protocol (GMP).

• osp: API support for the Open Scanner Protocol (OSP).

For more information on using the functionality provided by the gvm-libs module please refer to the source code documentation.

For any question on the usage of gvm-libs please use the Greenbone Community Portal. If you found a problem with the software, please create an issue on GitHub. If you are a Greenbone customer you may alternatively or additionally forward your issue to the Greenbone Support Portal.

This project is maintained by Greenbone Networks GmbH.

Your contributions are highly appreciated. Please create a pull request on GitHub. Bigger changes need to be discussed with the development team via the issues section at github first.

Before creating a pull request, it is recommended to run the following command:

make format

This reformats the new code to ensure that it follows the code style and formatting guidelines.

If you want to use the Clang Static Analyzer (http://clang-analyzer.llvm.org/) to do a static code analysis, you can do so by prefixing the configuration and build commands with scan-build:

scan-build cmake ..
scan-build make

The tool will provide a hint on how to launch a web browser with the results.

It is recommended to do this analysis in a separate, empty build directory and to empty the build directory before scan-build call.

Copyright (C) 2009-2019 Greenbone Networks GmbH

Licensed under the GNU General Public License v2.0 or later.