Secure-Compliance-Solutions-LLC / GVM-Docker

Greenbone Vulnerability Management Docker Image with OpenVAS
https://securecompliance.gitbook.io/projects/
MIT License
249 stars 91 forks source link

Optional Squid proxy on port 3128 to access from remote scanner #345

Closed vendito-david closed 1 year ago

vendito-david commented 2 years ago

Certain restricted environments have no internet connectivity and updating the image is problematic in those environments with rsync.

The OpenVAS image could use the existing SSH tunnel (forward a local port next to the unix socket) to access a Squid proxy running on the main GVM instance. Starting the proxy would be optional and in case it is not started, it wouldn't be possible to access it from the OpenVAS.

Summary

Adding optional squid proxy which starts when SQUID=true env variable is set. Using port 3128. Can be used from remote scanner if the port is forwarded in the existing tunnel.

Checklist

Fixed Bug/Issues solved:

Created issues: #16 in OpenVAS-Docker and #344 in GVM-Docker. https://github.com/Secure-Compliance-Solutions-LLC/OpenVAS-Docker/issues/16 https://github.com/Secure-Compliance-Solutions-LLC/GVM-Docker/issues/344

vendito-david commented 2 years ago

Relevant PR in OpenVAS-Docker: https://github.com/Secure-Compliance-Solutions-LLC/OpenVAS-Docker/pull/17 Relevant PR for gitbook: https://github.com/Secure-Compliance-Solutions-LLC/gitbook/pull/22

korzorro commented 1 year ago

The project is deprecated and no longer accepting pull requests.