-
Notifications
You must be signed in to change notification settings - Fork 34
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
Block wan access #29
Comments
what about you extends the vault docker image and apply some iptables rules? |
That would be a great solution. I will look for that, would be nice to have in the |
I believe a better solution would consist in blocking internet access during the creation of the container, so even if this repository gets hacked or someone tries to add a hidden code the restriction will be applied by the docker daemon not the image itself. |
The internet must be blocked at all time in the vault container, since it has access to our .ssh folder. It should only be able to communicate with the localhost for build and other docker containers.
|
How can we run this server and block to internally it doesn't access the internet?
My concern is to rely on a external docker image to provide sensitive project keys. If the ONVAULT container get hacked and introduce some way to push those keys to another internet server (like hidden code in the npm dependencies), I would like to not allow the container to connect the internet at all.
Do you know somehow to ensure that security inside the container?
The text was updated successfully, but these errors were encountered: