-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Report outdated / end-of-life Scan Engine / Environment (local) #312
Comments
It's already pushed to Docker Hub.
|
Thank you @austinsonger. So its back to debian and not alpine anymore? I'm also looking at the documentation at https://securecompliance.gitbook.io/projects/ but I can't find reference to what "master", "data" and "full" are or have I missed it in the docs? Will the scanners (https://github.com/Secure-Compliance-Solutions-LLC/OpenVAS-Docker) be similarly updated to 21.4.4? Thank you! |
Documentation will be updated in next release and OpenVAS repo is being worked on. |
Thank you! |
Hello, Thank you for your feedback, I have to with version 21.4.3-v1 since it is 3 months old securecompliance/gvm latest ed6308f4227f 3 months ago 486MB Labels": { |
but what are the differences between the images? |
Do we still need the mounted volumes ./storage/* or gvm when using the debian-master pull? |
@austinsonger Would it be easy to tag the dockerhub image with it's version number so that production systems wont break in case you update the master again? thanks, |
Which one do I tide download? Can the old Docker image delete it? |
I can't get my old databases to work with these latest debian versions, so it becomes a clean install for me. From the main page of this github repo for gvm-docker, under "Quick Start":
If you don't want to spend a lot of time downloading from scratch all the necessary data, get the "gvm:debian-master-data-full" just remember the initial setup password is "adminpassword" and you should change it once you log into the system. From what I understand you can't use the environment argument "PASSWORD=xxxxxx" to set the password on startup, but you can use the environment argument "DB_PASSWORD=yyyyyyy" to set the postgres db password (initial password is empty). Cheers! |
It is possible to migrate, but it is somewhat of a pain. You have to dump the database, then edit the dump file a bit since the newer image is running an older PostgreSQL version (LOCALE -> LC_COLLATE in the create database statement). Then you have to start the new container, get into a shell, stop the various services and load the database. I ran into various problems along the way, but ultimately was able to retain the original database contents moving from latest to debian-master. |
Ah, so you just needed to Which services did you stop and how exactly did you stop the services? I tried to stop gvmd and it kept respawning.
What other problems? I'm trying to script a restore for previous versions of the db right into the image using environment variables, any suggestions would be welcome! Thanks! |
Hi. After downgrade from PG 13 (21.4.3-v1-data-full) to PG 11(debian-master-data-full), I change patch for scanner. I get Interrupted at 0 % all time. |
Can anyone help me install the new zero docker? |
|
If you can live without your old reports and start clean from scratch (create all the targets, scans, etc again) then delete your current docker image and pul and start the new one:
And then go to your site port 8080 and log in as administrator with password 'adminpassword'. Remember to change your password after you log in. |
|
If you can read, you can fix it your self!
Absolute path not relative path!
Von meinem iPhone gesendet
… Am 22.12.2021 um 15:27 schrieb Fantasmagyn ***@***.***>:
Can anyone help me install the new zero docker? Do I need the old one made in Alpine first? I do not understand how to solve this issue.
If you can live without your old reports and start clean from scratch (create all the targets, scans, etc again) then delete your current docker image and pul and start the new one:
docker run --detach --publish 8080:9392 --publish 5432:5432 --publish 2222:22 --volume ./storage/postgres-db:/opt/database --volume ./storage/openvas-plugins:/var/lib/openvas/plugins --volume ./storage/gvm:/var/lib/gvm --volume ./storage/ssh:/etc/ssh --name gvm securecompliance/gvm:debian-master-data-full
And then go to your site port 8080 and log in as administrator with password 'adminpassword'. Remember to change your password after you log in.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.
|
English might not be his strong suite. @meetgyn instead of using
Hope that helps. |
Thanks for your help. I really am horrible in English, and I apologize for it. |
No apologies necessary, we help each other when we can. Hope you got it running. Cheers! |
You can now use the https://hub.docker.com/r/deineagenturug/gvm images, which are using the latest gvmd and components releases. It use POSTGRESQL 13. What are meaning the tags:
It can be used as direct replacement for the here provided image, with the same arguments on |
I am trying to reinstall Greenbone, I managed with the command: Docker Run --Detach --Publish 8080: 9392 --publish 5432: 5432 --Publish 2222: 22 --Volume / VAR / LIB / Docker / Volumes / GVM / Storage / Postgres-DB: / opt / database --volume / var / lib / docker / volumes / gvm / storage / openvas-plugins: / var / lib / openvas / plugins - vector GVM / Storage / GVM: / var / lib / gvm --volume / var / lib / docker / volumes / gvm / storage / ssh: / etc / ssh - Name GVM SecureCompliance / GVM: Debian-Master-Data-Full |
@meetgyn if you read here, you know whats wrong. by the way: with usage of volumes, you don't get the benefits of the |
@meetgyn think you’re using the wrong image. Use deineagenturug/gvm:latest-data-full not secure compliance/gvm |
For further support, use https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker |
Why the docker image I pull on June 20 is still openvas-scanner version:21.4.2 |
Describe the bug
Good evening, all scans on any host always return the same warning message.
Report outdated / end-of-life Scan Engine / Environment (local)
Summary
Greenbone Source Edition (GSE)
Greenbone Security Manager TRIAL (formerly Greenbone Community Edition (GCE))
used for this scan.
NOTE: While this is not, in and of itself, a security vulnerability, a severity is reported to
make you aware of a possible decreased scan coverage or missing detection of vulnerabilities on
the target due to e.g.:
missing functionalities
missing bugfixes
incompatibilities within the feed
Detection Result
Detection Method
Solution
If you want to accept the risk of a possible decreased scan coverage or missing detection of
vulnerabilities on the target you can set a global override for this script as described in the
linked GSM manual.
Screenshots
Host Device:
VERSION="2021.3"
VERSION_ID="2021.3"
VERSION_CODENAME="kali-rolling"
ID_LIKE=debian
docker image inspect![]()
version: "3"
services:
gvm:
image: securecompliance/gvm
volumes:
- ./postgres:/opt/database
- ./gvm:/var/lib/gvm
- ./plugins:/var/lib/openvas/plugins
environment:
- USERNAME="admin"
- PASSWORD="admin"
- RELAYHOST="smtp"
- SMTPPORT=25
- AUTO_SYNC=true
- HTTPS=true
- TZ=""
- SSHD=false
- DB_PASSWORD="none"
ports:
- "8099:9392" # Web interface
#- "5432:5432" # Access PostgreSQL database from external tools
#- "2222:22" # SSH for remote sensors
restart: unless-stopped
The text was updated successfully, but these errors were encountered: