Sandbox deny rules now block every directory a symlink chain passes through, not just the endpoint.
What's wrong with this entry?
When a denied path is a symlink chain, the sandbox now denies the directories crossed along the way, not just the final target. Applies to everyone; on Windows no hop set is computed.
- The walk is capped by a hop budget and stops on anything other than the expected missing-or-not-a-directory errors.
- A new resolver handles dangling paths before the old parent-directory fallback.
hopDirectories
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox