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
Just adding local 3128 port forwarded to main GVM 3128 port in the ssh tunnel for optional rsync proxy.
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
Just adding local 3128 port forwarded to main GVM 3128 port in the ssh tunnel for optional rsync proxy.
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