Repository navigation
macOS: a read rule on a link to a device stays on the link - #694
Merged
ronleizrowice-ant merged 1 commit intoOct 12, 2026
Merged
Conversation
A read rule also applies where its path leads. Where that is a device, the rule would be one on the device for every command: a denyRead on a name blanked with a link to /dev/null denied reading /dev/null. The second spelling is not added at or under /dev, as it already is not for the root.
ronleizrowice-ant
deleted the
fix/macos-a-read-rule-on-a-link-to-a-device
branch
October 12, 2026 14:15
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
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.
Since #680 a read rule on macOS also applies where its path leads. Where that is a device, the rule lands on the device for every command:
denyReadon.env -> /dev/null, a common way to blank a file, denies reading/dev/null. A rule on a link to/devdenies all of/dev. Not in a release yet.What changes (+9/-1)
The second spelling is not added where it lies at or under
/dev, as it already is not for/. The rule on the link itself stays. The same forcredentials.filesentries, deny or mask, and for patterns.Who sees a difference
macOS only, and only with a read rule on a link into
/dev: as in 0.0.79. A device named by its own path is denied as before.Testing
cat /dev/nullandcat < /dev/nullwork.mainand here: the six on devices read as on 0.0.79. A link to an ordinary file keeps both spellings.Not covered
Linux: a
denyReadon a link to/dev/nullplans a mount on/dev/null, which bubblewrap 0.4.1 refuses. As onmain.#693 holds the same lines.