-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix(security): warn when Landlock may silently degrade #868
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
Open
fdzdev
wants to merge
1
commit into
NVIDIA:main
Choose a base branch
from
fdzdev:fix/landlock-degradation-warn
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+27
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
macOS Landlock warning is too narrow and misses the stated security signal.
Line [2283]–Line [2293] only warns on macOS when Docker VM kernel parses as
< 5.13. The PR objective/test plan says macOS hosts should warn regardless, so this can silently skip the warning on macOS with kernel>= 5.13(or unparsable versions).Suggested fix
try { if (process.platform === "darwin") { const vmKernel = runCapture("docker info --format '{{.KernelVersion}}'", { ignoreError: true }).trim(); - if (vmKernel) { - const parts = vmKernel.split("."); - const major = parseInt(parts[0], 10); - const minor = parseInt(parts[1], 10); - if (!isNaN(major) && !isNaN(minor) && (major < 5 || (major === 5 && minor < 13))) { - console.warn(` ⚠ Landlock: Docker VM kernel ${vmKernel} does not support Landlock (requires ≥5.13).`); - console.warn(" Sandbox filesystem restrictions will silently degrade (best_effort mode)."); - } - } + console.warn( + vmKernel + ? ` ⚠ Landlock: macOS host (Docker VM kernel ${vmKernel}). Landlock enforcement may silently degrade (best_effort mode).` + : " ⚠ Landlock: macOS host. Landlock enforcement may silently degrade (best_effort mode)." + ); } else if (process.platform === "linux") { const uname = runCapture("uname -r", { ignoreError: true }).trim(); if (uname) { const parts = uname.split(".");📝 Committable suggestion
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
intentional per cv's review — the point is to check the Docker VM kernel and only warn when it doesn't support Landlock (< 5.13). If the VM kernel supports it, there's nothing to warn about. Unconditional warnings are noise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fdzdev, understood — the conditional check is the right call. Warn only when the Docker VM kernel is verifiably< 5.13, wherebest_effortactually degrades; stay silent when the VM kernel supports Landlock so there's no false-alarm noise on modern Docker Desktop setups. I'll retract the suggestion.✏️ Learnings added