diff --git a/src/22.4/container/admin-user.md b/src/22.4/container/admin-user.md index 9283b9e3..e6131f39 100644 --- a/src/22.4/container/admin-user.md +++ b/src/22.4/container/admin-user.md @@ -12,7 +12,7 @@ generated password, the following command can be used: --- caption: Updating password of administrator user --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ exec -u gvmd gvmd gvmd --user=admin --new-password='' ``` diff --git a/src/22.4/container/docker-compose.yml b/src/22.4/container/docker-compose.yml index 8e7a4155..4acec7c2 120000 --- a/src/22.4/container/docker-compose.yml +++ b/src/22.4/container/docker-compose.yml @@ -1 +1 @@ -../../_static/docker-compose-22.4.yml \ No newline at end of file +../../_static/docker-compose.yml \ No newline at end of file diff --git a/src/22.4/container/index.md b/src/22.4/container/index.md index 45ee8fa8..0665f0ed 100644 --- a/src/22.4/container/index.md +++ b/src/22.4/container/index.md @@ -14,6 +14,12 @@ ## Docker Compose File +```{important} +Please always ensure to use the latest version of the `docker-compose.yml` file +when following this guide. The file might got updates and important changes +since your last download. +``` + To run the Greenbone Community Edition with containers, the following compose file should be used: @@ -33,7 +39,7 @@ it can be downloaded with the following command directly: --- caption: Downloading docker-compose file --- -cd $DOWNLOAD_DIR && curl -f -L https://greenbone.github.io/docs/latest/_static/docker-compose-22.4.yml -o docker-compose.yml +curl -f -O -L https://greenbone.github.io/docs/latest/_static/docker-compose.yml --output-dir "$DOWNLOAD_DIR" ``` ### Description diff --git a/src/22.4/container/manual-feed-sync.md b/src/22.4/container/manual-feed-sync.md index 129bc593..28940d51 100644 --- a/src/22.4/container/manual-feed-sync.md +++ b/src/22.4/container/manual-feed-sync.md @@ -20,7 +20,7 @@ caption: Extending the docker compose file for performing a manual feed sync usi --- ... greenbone-feed-sync: - image: greenbone/greenbone-feed-sync + image: registry.community.greenbone.net/community/greenbone-feed-sync volumes: - vt_data_vol:/var/lib/openvas/plugins - notus_data_vol:/var/lib/notus @@ -41,7 +41,7 @@ during a vulnerability scan. caption: Downloading {term}`NASL` {term}`VTs` processed by the ospd-openvas scanner, this will take a while. --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ run --rm greenbone-feed-sync greenbone-feed-sync --type nasl ``` @@ -50,9 +50,10 @@ docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-editio caption: Downloading `notus` {term}`VTs` processed for local security checks, this will take a while. --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ run --rm greenbone-feed-sync greenbone-feed-sync --type notus ``` + ### Syncing SCAP, CERT and GVMD Data {term}`SCAP` data contains {term}`CPE` and {term}`CVE` information. @@ -61,7 +62,7 @@ docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-editio --- caption: Downloading SCAP data processed by gvmd, this will take a while --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ run --rm greenbone-feed-sync greenbone-feed-sync --type scap ``` @@ -72,7 +73,7 @@ and [CERT-Bund](https://cert-bund.de/) agencies. --- caption: Downloading CERT data processed by gvmd --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ run --rm greenbone-feed-sync greenbone-feed-sync --type cert ``` @@ -83,6 +84,6 @@ policies, port lists and report formats. --- caption: Downloading data objects processed by gvmd --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ run --rm greenbone-feed-sync greenbone-feed-sync --type gvmd-data ``` diff --git a/src/22.4/container/preamble.md b/src/22.4/container/preamble.md index 8ef5b73a..da887c7c 100644 --- a/src/22.4/container/preamble.md +++ b/src/22.4/container/preamble.md @@ -15,7 +15,7 @@ intended for production setups. Currently the docs support the following distributions * **Debian stable** [(bookworm)](https://www.debian.org/releases/stable) -* **Ubuntu 22.04 LTS** +* **Ubuntu 24.04 LTS** * **Fedora 35 and 36** * **CentOS 9 Stream** diff --git a/src/22.4/container/starting.md b/src/22.4/container/starting.md index 43e4d6fd..75e5853e 100644 --- a/src/22.4/container/starting.md +++ b/src/22.4/container/starting.md @@ -7,14 +7,14 @@ and the containers can be started in the background. --- caption: Downloading the Greenbone Community Containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition pull +docker compose -f $DOWNLOAD_DIR/docker-compose.yml pull ``` ```{code-block} shell --- caption: Starting the Greenbone Community Containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d ``` To get a continuous stream of the log output of all services, run the following @@ -24,8 +24,7 @@ command: --- caption: Show log messages of all services from the running containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition logs -f +docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs -f ``` The log stream can be stopped by pressing {kbd}`Ctrl-C`. - diff --git a/src/22.4/container/troubleshooting.md b/src/22.4/container/troubleshooting.md index 9d7a78f1..a0423a57 100644 --- a/src/22.4/container/troubleshooting.md +++ b/src/22.4/container/troubleshooting.md @@ -15,8 +15,7 @@ command. For displaying the complete log output you can run --- caption: Display all logs --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - logs +docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs ``` To follow the current log output to display log messages as they occur use the @@ -26,8 +25,7 @@ following command --- caption: Follow current log output --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - logs -f +docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs -f ``` It's also possible to just display the logs of a specific container by using @@ -38,8 +36,7 @@ within the docker compose file](./index.md#description). --- caption: Follow the log messages of the gvmd container only --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - logs -f gvmd +docker compose -f $DOWNLOAD_DIR/docker-compose.yml logs -f gvmd ``` Additionally it is possible to bypass the `docker compose log` command and @@ -50,7 +47,7 @@ the content of the OpenVAS scanner log file via {command}`cat` --- caption: Print messages from /var/log/gvm/openvas.log --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ exec ospd-openvas cat /var/log/gvm/openvas.log ``` @@ -70,8 +67,7 @@ scanner. --- caption: Restart the scanner to ensure that new {term}`VTs` are loaded --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - restart ospd-openvas +docker compose -f $DOWNLOAD_DIR/docker-compose.yml restart ospd-openvas ``` ### Port list, scan configurations, report formats are up-to-date but not visible on the web interface @@ -82,7 +78,7 @@ If port lists, scan configurations, or report formats are missing on the web int --- caption: Forcing reload of report formats, scan configs and port lists --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ exec -u gvmd gvmd gvmd --rebuild-gvmd-data=all ``` @@ -109,8 +105,7 @@ restart the corresponding container with: --- caption: Restarting the ospd-openvas scanner --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - restart ospd-openvas +docker compose -f $DOWNLOAD_DIR/docker-compose.yml restart ospd-openvas ``` If you still get errors, you need to take a look at the `ospd-openvas` logs. @@ -119,8 +114,7 @@ If you still get errors, you need to take a look at the `ospd-openvas` logs. --- caption: Showing log message of the ospd-openvas scanner --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - log -f ospd-openvas +docker compose -f $DOWNLOAD_DIR/docker-compose.yml log -f ospd-openvas ``` ### Cannot log in to the web interface: *Greenbone Vulnerability Manager service is not responding* @@ -144,8 +138,7 @@ had some issues accessing the PostgreSQL database. --- caption: Restarting {term}`gvmd` --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - restart gvmd +docker compose -f $DOWNLOAD_DIR/docker-compose.yml restart gvmd ``` ### Redis server keeps restarting `rm: cannot remove ‘/run/redis/redis.sock’: Permission denied` @@ -160,9 +153,8 @@ The volume can be removed safely because it gets recreated on the next startup. --- caption: Recreating the Redis server socket volume --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose.yml \ rm -s -f redis-server ospd-openvas docker volume rm greenbone-community-edition_redis_socket_vol -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ - up -d +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d ``` diff --git a/src/22.4/container/workflows.md b/src/22.4/container/workflows.md index 194b9df1..9a891a83 100644 --- a/src/22.4/container/workflows.md +++ b/src/22.4/container/workflows.md @@ -10,14 +10,14 @@ be done with: --- caption: Downloading the Greenbone Community Containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition pull +docker compose -f $DOWNLOAD_DIR/docker-compose.yml pull ``` ```{code-block} shell --- caption: Starting the Greenbone Community Containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d ``` ## Performing a Feed Synchronization @@ -52,7 +52,7 @@ To download the latest feed data container images run --- caption: Downloading the Greenbone Community Edition feed data containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition pull notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects +docker compose -f $DOWNLOAD_DIR/docker-compose.yml pull notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects ``` To copy the data from the images to the volumes run @@ -61,7 +61,7 @@ To copy the data from the images to the volumes run --- caption: Starting the Greenbone Community feed data containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects ``` ### Loading the Feed Changes @@ -90,6 +90,7 @@ take a few minutes, please wait... ``` The loading of the VT data is finished if the log message can be found: + ```{code-block} none --- caption: ospd-openvas VTs loading finished log message @@ -232,10 +233,10 @@ by running: --- caption: Remove containers and volumes (all data) --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition down -v +docker compose -f $DOWNLOAD_DIR/docker-compose.yml down -v ``` -## Gaining a Terminal for a Container +## Gaining a Terminal for a Container If you want to debug something in a container, install additional software, take a look at the file content, or change some configuration, it is possible to gain @@ -247,7 +248,7 @@ To access a container with a bash shell as a root user, you can run: --- caption: Gain a Terminal for a Container --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition exec /bin/bash +docker compose -f $DOWNLOAD_DIR/docker-compose.yml exec /bin/bash ``` Afterwards, you can execute standard bash commands within the running container. @@ -262,7 +263,7 @@ can be started with: --- caption: Start container for gvm-tools CLI access --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition run --rm gvm-tools +docker compose -f $DOWNLOAD_DIR/docker-compose.yml run --rm gvm-tools ``` Afterwards, a bash shell is provided and `gvm-cli`, `gvm-pyshell` or `gvm-script` @@ -322,7 +323,7 @@ In the next step, the docker compose file must be changed as follows: After restarting the containers with ```bash -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d ``` the Unix socket should be available at `/tmp/gvm/gvmd/gvmd.sock`. For example, @@ -360,7 +361,7 @@ caption: Use a local network relay without authorization --- ... gvmd: - image: greenbone/gvmd:stable + image: registry.community.greenbone.net/community/gvmd:stable environment: - MTA_HOST=postfix-server.example.org - MTA_PORT=25 @@ -369,13 +370,14 @@ caption: Use a local network relay without authorization - MTA_AUTH=off ... ``` + ```{code-block} yaml --- caption: Use the Google Mail services with SSL and authorization --- ... gvmd: - image: greenbone/gvmd:stable + image: registry.community.greenbone.net/community/gvmd:stable environment: - MTA_HOST=smtp.gmail.com - MTA_PORT=587 @@ -393,34 +395,48 @@ caption: Use the Google Mail services with SSL and authorization ## Setting up SSL/TLS for GSA -Enabling SSL/TLS for the the web interface ({term}`GSA`) requires generating a private key and public certificate, and adjusting the `gsa` container settings in the `docker-compose.yml` file. +Enabling SSL/TLS for the the web interface ({term}`GSA`) requires generating a +private key and public certificate, and adjusting the `gsa` container settings +in the `docker-compose.yml` file. -As of September 2020, the maximum validity period for publicly trusted SSL/TLS certificates is 398 days. An expiration date of more than 397 days is not valid and may cause some browsers to block the connection. OpenSSL can be used to generate the private key and certificate: +As of September 2020, the maximum validity period for publicly trusted SSL/TLS +certificates is 398 days. An expiration date of more than 397 days is not valid +and may cause some browsers to block the connection. OpenSSL can be used to +generate the private key and certificate: ```{code-block} yaml openssl req -x509 -newkey rsa:4096 -keyout serverkey.pem -out servercert.pem -nodes -days 397 ``` -The user that executes the `docker compose` command must have read access to the private key and certificate. So, they must be placed in an appropriate location such as the user's home directory or the `tmp` directory. +The user that executes the `docker compose` command must have read access to the +private key and certificate. So, they must be placed in an appropriate location +such as the user's home directory or the `tmp` directory. ```{code-block} yaml -mkdir $HOME/.ssl && mv serverkey.pem servercert.pem $HOME/.ssl +mkdir $HOME/.ssl && mv serverkey.pem servercert.pem $HOME/.ssl ``` -Finally, the {term}`GSA` configuration in the `docker-compose.yml` file must be modified to enable SSL/TLS. The changes include: +Finally, the {term}`GSA` configuration in the `docker-compose.yml` file must be +modified to enable SSL/TLS. The changes include: -1. Setting the `GSAD_ARGS` environment variable to initialize SSL/TLS. In the example below, three arguments are set. A complete list of {term}`GSAD` arguments are in the gsad manpage (execute `gsad --help` from within the GSA container), and in the [GSAD documentation](https://github.com/greenbone/gsad/tree/main/doc) in its GitHub repository. The arguments used in this example are: +1. Setting the `GSAD_ARGS` environment variable to initialize SSL/TLS. In the +example below, three arguments are set. A complete list of {term}`GSAD` +arguments are in the gsad manpage (execute `gsad --help` from within the GSA +container), and in the [gsad documentation](https://github.com/greenbone/gsad/tree/main/doc) +in its GitHub repository. The arguments used in this example are: - `--no-redirect`: Don't redirect HTTP to HTTPS and only allow HTTPS connections to the web interface - `--http-sts`: Enables HSTS (HTTP Strict Transport Security) for the GSAD web-server - - `--gnutls-priorities`: Disables insecure versions of TLS (1.0 and 1.1) -2. Copying the private key and certificate files from the host system into the GSA container upon initialization. -3. Changing the web interface port to the standard SSL/TLS port 443 and optionally enabling remote access - + - `--gnutls-priorities`: Disables insecure versions of TLS (1.0 and 1.1) +2. Copying the private key and certificate files from the host system into the +GSA container upon initialization. +3. Changing the web interface port to the standard SSL/TLS port 443 and +optionally enabling remote access Sample `gsa` container settings to enable SSL/TLS: + ```diff gsa: - image: greenbone/gsa:stable + image: registry.community.greenbone.net/community/gsa:stable restart: on-failure + environment: + - GSAD_ARGS=--no-redirect --http-sts --gnutls-priorities=SECURE256:-VERS-TLS-ALL:+VERS-TLS1.2:+VERS-TLS1.3 @@ -440,11 +456,12 @@ gsa: - gvmd ``` -After modifying the `docker-compose.yml` file, restart the containers to enable the changes. +After modifying the `docker-compose.yml` file, restart the containers to enable +the changes. ```{code-block} shell --- caption: Restart the Greenbone Community Containers --- -docker compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition up -d +docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d ``` diff --git a/src/_static/docker-compose-22.4.yml b/src/_static/docker-compose-22.4.yml index 5940b854..32648fd2 100644 --- a/src/_static/docker-compose-22.4.yml +++ b/src/_static/docker-compose-22.4.yml @@ -1,3 +1,5 @@ +name: greenbone-community-edition + services: vulnerability-tests: image: registry.community.greenbone.net/community/vulnerability-tests diff --git a/src/_static/setup-and-start-greenbone-community-edition.sh b/src/_static/setup-and-start-greenbone-community-edition.sh index 60b6b6af..0babecf0 100755 --- a/src/_static/setup-and-start-greenbone-community-edition.sh +++ b/src/_static/setup-and-start-greenbone-community-edition.sh @@ -1,5 +1,5 @@ #!/bin/bash -# Copyright (C) 2022 - 2023 Greenbone AG +# Copyright (C) 2022 - 2025 Greenbone AG # # SPDX-License-Identifier: GPL-3.0-or-later # @@ -53,18 +53,18 @@ echo "Using Greenbone Community Containers $RELEASE" mkdir -p $DOWNLOAD_DIR && cd $DOWNLOAD_DIR echo "Downloading docker-compose file..." -curl -f -O https://greenbone.github.io/docs/latest/_static/docker-compose-$RELEASE.yml +curl -f -O https://greenbone.github.io/docs/latest/_static/docker-compose.yml echo "Pulling Greenbone Community Containers $RELEASE" -docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml -p greenbone-community-edition pull +docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml pull echo echo "Starting Greenbone Community Containers $RELEASE" -docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml -p greenbone-community-edition up -d +docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml up -d echo read -s -p "Password for admin user: " password -docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml -p greenbone-community-edition \ +docker compose -f $DOWNLOAD_DIR/docker-compose-$RELEASE.yml \ exec -u gvmd gvmd gvmd --user=admin --new-password=$password echo diff --git a/src/changelog.md b/src/changelog.md index ef4c46d3..e1190eb1 100644 --- a/src/changelog.md +++ b/src/changelog.md @@ -6,6 +6,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Calendar Versioning](https://calver.org). ## Latest + * Corrected the path for moving the openvasd built files * Add instructions for Kali Linux installation * Add instructions to enable SSL/TLS @@ -26,8 +27,15 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Update OpenVAS Scanner to 23.0.1 * Drop notus-scanner in favor of the new OpenVAS Daemon (openvasd). This made the Mosquitto MQTT broker obsolete too. * Drop mention of obsolete dependency on xml-twig-tools / perl-XML-Twig +* Update supported Ubuntu version for docker compose guide to 24.04 +* Use unversioned `docker-compose.yml` file for the download +* Set [docker compose project](https://docs.docker.com/reference/compose-file/version-and-name/#name-top-level-element) +via compose file. This allows to remove the `-p greenbone-community-edition` +argument from all docker compose commands. +* Update image names in examples where the compose file is adjusted + +## 23.11.0 - 23-11-21 -## 23.11.0 * Add workflow page for source builds * Add documentation for updating source builds * Don't expose MQTT broker port in docker compose setup by default @@ -45,6 +53,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Add general troubleshooting page ## 23.9.0 - 23-09-23 + * Update pg-gvm to 22.6.1 * Improve description of GSA and its build process in the source build * Use Debian 12 bookworm also for the community container docs @@ -58,6 +67,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Replace docker-compose v1 with Docker Compose v2 ## 23.7.0 – 23-07-25 + * Update gvmd to 22.6.0 * Update gsad to 22.5.1 * Update GSA to 22.5.3 @@ -71,6 +81,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). community containers ## 23.6.2 – 23-06-27 + * Update to use Debian 12 (bookworm) * Install GSA from pre-built distributable files * Update openvas-smb to 22.5.3 @@ -82,6 +93,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Update source build instructions for Fedora 38 ## 23.6.1 – 23-06-15 + * Update gvm-libs to 22.6.3 * Update notus-scanner to 22.5.0 * Update openvas-scanner to 22.7.2 @@ -90,6 +102,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Don't install old `greenbone-nvt-sync` script anymore ## 23.6.0 – 23-06-15 + * Fix tab title in *Setting up sudo for Scanning* section from Debian/CentOS to Debian/Ubuntu. * Update notus-scanner to 22.4.5 @@ -98,6 +111,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Add a section about update help to FAQ ## 23.3.0 – 23-03-08 + * Unify the directory layout of the documentation files * Use distinct installation directories for each component * Add missing python3-gnupg as dependency to ospd-openvas @@ -115,6 +129,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). build to allow using $INSTALL_PREFIX when setting the $PATH. ## 23.1.1 – 23-01-31 + * Set `table_drive_lsc = yes` setting for openvas scanner to enable local security checks scanning via notus scanner * Remove docs for 21.04 because it is end-of-life and wont get any updates @@ -127,10 +142,12 @@ and this project adheres to [Calendar Versioning](https://calver.org). services ## 23.1.0 – 23-01-13 + * Fix installing ospd-openvas and notus-scanner on Debian 11 * Update components to 22.4.1 release ## 22.12.0 – 22-12-27 + * Fix setting executable permission for setup and install script after the download * Check for docker being installed in setup and install script @@ -153,6 +170,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Update docker compose requirement to 1.29.0 ## 22.8.2 – 22-08-31 + * Improve feed sync documentation for source build * Use feed data containers for feed sync in Greenbone Community Containers docs * Extract workflows and troubleshooting to own pages for Greenbone Community @@ -162,6 +180,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Use notus-scanner 22.4.1 and ospd-openvas 22.4.1 for 22.4 source build ## 22.8.1 – 2022-08-29 + * Add workflow for exposing the gvmd unix socket from the container * Add an API page for links to our other community documentation * Fix path of the notus-scanner product advisories directory for the 22.4 @@ -169,6 +188,7 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Add gvm-tools container and usage workflow documentation ## 22.8.0 – 2022-08-16 + * Fix Community Container setup and start script * Fix installing yarn from third party debian package repository * Improve and extend feed sync chapters for community containers @@ -179,9 +199,11 @@ and this project adheres to [Calendar Versioning](https://calver.org). new features like dark mode ## 22.7.0 – 2022-07-25 + * Update docs for supporting 22.4 release ## 22.5.0 – 2022-05-30 + * New Greenbone Community Containers documentation * Update index page, history, architecture, faq and glossary for adjusted terms and naming. @@ -189,38 +211,46 @@ and this project adheres to [Calendar Versioning](https://calver.org). * Re-arrange page structure and therefore the URLs of the documents ## 22.3.3 – 2022-03-31 + * Fix setting cmake parameter of runtime directory for gvmd * Fix starting the correct postgresql cluster ## 22.3.2 – 2022-03-30 + * The build guide uses Debian Stable (Bullseye) * Fix installing dependencies of gvmd and openvas-scanner for Debian Bullseye * Remove obsolete cmake parameter when building gvm-libs to avoid a warning ## 22.3.1 – 2022-03-21 + * Fix runtime directory for gvmd in systemd service file * Add runtime directory and mode for gsad in systemd service file ## 22.3.0 – 2022-03-07 + * Fix source paths for gsad * Fix build and installation of GSA * Add hint about yarn package on Debian * Fix PIDFile settings in systemd service files for gsad and gvmd ## 22.2.0 – 2022-02-24 + * Drop GVM 20.8. * Split of GSA and gsad * Merge of ospd and ospd-openvas ## 21.10.1 – 2021-10-13 + * Drop usage of gsa-node-modules. These tarballs are only useful for specific nodejs versions. ## 21.10.0 – 2021-10-12 + * Update for GVM 21.4.3 and 20.8.4 releases * Mark GVM 20.08 as end-of-life. User should switch to 21.04. ## 21.8.0 – 2021-08-05 + * Update for GVM 21.4.2 and 20.8.3 releases * Changed feed look file location to `/var/lib/gvm/feed-update.lock`. This file is used by `gvmd` and `greenbone-feed-sync` @@ -229,4 +259,5 @@ and this project adheres to [Calendar Versioning](https://calver.org). the admin user ## 21.7.0 – 2021-07-05 + * Initial version