Skip to content
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

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

Closed

Conversation

vendito-david
Copy link

@vendito-david vendito-david commented Jul 15, 2022

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.
Secure-Compliance-Solutions-LLC/OpenVAS-Docker#16
#344

@vendito-david
Copy link
Author

vendito-david commented Jul 15, 2022

Relevant PR in OpenVAS-Docker: Secure-Compliance-Solutions-LLC/OpenVAS-Docker#17
Relevant PR for gitbook: Secure-Compliance-Solutions-LLC/gitbook#22

Dockerfile Outdated Show resolved Hide resolved
Co-authored-by: Josef Fröhle <github@josef-froehle.de>
@korzorro korzorro closed this Aug 18, 2023
@korzorro
Copy link
Member

The project is deprecated and no longer accepting pull requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants