Skip to content

mongo: add security section #2399

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

Merged
merged 1 commit into from
Dec 20, 2023
Merged

mongo: add security section #2399

merged 1 commit into from
Dec 20, 2023

Conversation

whalelines
Copy link
Contributor

@whalelines
Copy link
Contributor Author

By my calculations, this does not cause the README without the tags to exceed the Hub size limit.

@tianon tianon merged commit 86467a5 into docker-library:master Dec 20, 2023
@tianon
Copy link
Member

tianon commented Dec 20, 2023

Nice, thank you!

@godmar
Copy link

godmar commented Dec 21, 2023

While a good start, that section is insufficient because it does not address the behavior on -p hostport:containerport. I suggest looking at the Redis documentation for an example to follow.

The pitfall here is not just that you ship with authentication disabled: it's that the common defense mechanism of binding to the loopback interface does not work inside a container. As soon as you create a network path to the container -- which you have to do to be able to use your software at all - you run the risk of exposing the database to the Internet.

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.

Considering updating the documentation to state that the default configuration of this container is insecure
3 participants