-
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
[Enhancement] Squid proxy for restricted environments #344
Comments
Paired with issue #16 in OpenVAS-Docker. |
This was referenced Jul 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Standalone proxy could be also utilized with extra work, but this way only a single SSH connection is required for those restricted environments.
The text was updated successfully, but these errors were encountered: