Open huornlmj opened 2 years ago
For further support, use https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker
@Dexus are you sure about https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker ? That's an entirely different project, and their slogan "Webservices, Webhosting and Games for YOU!", and being translated to "Your agency", doesn't seem like a group involved in security. Are they taking over support from this repo? UPDATE - I see now that you are the owner of that company. Not sure I agree with the site's slogan from 2004
@Dexus are you sure about https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker ? That's an entirely different project, and their slogan "Webservices, Webhosting and Games for YOU!", and being translated to "Your agency", doesn't seem like a group involved in security. Are they taking over support from this repo?
my company -> my repository -> my support -> my freedom to work on the project without restrictions and other things, I'm not able to do here, since I never was an employee of SCS - and what you see is that they never bring any working solutions or updates themself. I'm doing much more, than ever a slogen can say in only six words :D
UPDATE - I see now that you are the owner of that company. Not sure I agree with the site's slogan from 2004
I'm owning the domain since 2008 and also my company since 2009 so it's not my message from 2004.
After spending some time following the guidance here (https://securecompliance.gitbook.io/projects/gvm_image) and observing the feeds failing to download due to RSYNC proxy issues, I wanted to share some feedback here. The documentation should contain a section for those operating behind proxies. I found that feeds only updated if I provided environment variables, specifically:
--env RSYNC_PROXY="proxy.internal.local:3128"
Note the omission of the protocol before proxy.internal.local
So in total, the working command for behind a proxy was:
docker run --detach --publish 8080:9392 --publish 5432:5432 --publish 2222:22 --env HTTP_PROXY="http://proxy.internal.local:3128" --env HTTPS_PROXY="http://proxy.internal.local:3128" --env RSYNC_PROXY="proxy.internal.local:3128" --env DB_PASSWORD="postgres DB password" --env PASSWORD="webUI password" --volume gvm-data:/data --name gvm securecompliance/gvm
By the way - thank you for making it so easy to deploy GVM! manual installation has become somewhat of an unnecessary 'rite of passage'.