Block non-local traffic to the Weave control port #3805
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bboreham
force-pushed
the
block-remote-localhost
branch
5 times, most recently
from
a2ea34f
to
74c55ec
Compare
We expect the loopback address 127.0.0.1 to be accessible only from the local host. We need to allow RELATED,ESTABLISHED traffic which may be the return path of a Kubernetes HostPort.
bboreham
force-pushed
the
block-remote-localhost
branch
from
74c55ec
to
6ee961b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We expect the loopback address 127.0.0.1 to only be accessible from the local host.
However under some Linux configurations it can be accessed remotely. kubernetes/kubernetes#90259
Add an iptables rule to block this case.