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

Block wan access #29

Open
gartz opened this issue Jan 23, 2017 · 4 comments
Open

Block wan access #29

gartz opened this issue Jan 23, 2017 · 4 comments

Comments

@gartz
Copy link

gartz commented Jan 23, 2017

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?

@krolow
Copy link
Contributor

krolow commented Jan 24, 2017

what about you extends the vault docker image and apply some iptables rules?

@gartz
Copy link
Author

gartz commented Jan 24, 2017

That would be a great solution. I will look for that, would be nice to have in the README.md the instructions for doing that.

@esnunes
Copy link
Member

esnunes commented Jan 24, 2017

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.

@gartz
Copy link
Author

gartz commented Jan 24, 2017 via email

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

No branches or pull requests

3 participants