Restrict ingress port forwarding when using --dev-password#496
Merged
nabuskey merged 1 commit intocnoe-io:mainfrom Mar 7, 2025
Merged
Restrict ingress port forwarding when using --dev-password#496nabuskey merged 1 commit intocnoe-io:mainfrom
nabuskey merged 1 commit intocnoe-io:mainfrom
Conversation
forwarding our ingress to the host node and listening on 0.0.0.0 can potentially be dangerous, particularly if a user is using the --dev-password flag to use an insecure static password. In that case someone could potentially access their gitea/argocd install and run arbitrary pods in the cluster. Signed-off-by: Caleb Boylan <calebboylan@gmail.com>
cmoulliard
pushed a commit
to ch007m/fork-idpbuilder
that referenced
this pull request
Mar 14, 2025
Signed-off-by: Caleb Boylan <calebboylan@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
forwarding our ingress to the host node and listening on 0.0.0.0 can potentially be dangerous, particularly if a user is using the --dev-password flag to use an insecure static password. In that case someone could potentially access their gitea/argocd install and run arbitrary pods in the cluster.