Reject explicit legacy probing on modern Docker hosts - #5
Merged
chen21019 merged 2 commits intoSep 12, 2026
Merged
Conversation
chen21019
deleted the
verification/ipsec-vxlan-overlay-network-explicit-backend
branch
September 12, 2026 07:35
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
1 participant
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.
Prevent a mistaken explicit iptables-legacy choice on an iptables-nft host from invoking the legacy frontend (which can load old modules merely for an inspection). Require an already-loaded legacy NAT table for old hosts; native nft and automatic selection stay unchanged. Add fail-closed tests and document the boundary. The protected release remains gated by same-SHA main CI and a published image digest.