Commands arriving with sandbox constraints are refused unless a fully confining sandbox exists.
What's wrong with this entry?
When a call arrives with constraints attached, Bash now refuses to run it unless a fully confining sandbox is available, and refuses outright if the constraints carry extra file read/write deny lists, which cannot yet be enforced locally. Both refusals emit sandbox telemetry and the command never starts.
- Only applies when the incoming call actually carries constraints; ordinary local Bash calls are unaffected.
- The deny-list refusal is unconditional rather than degrading to an unsandboxed run.
This call carries file deny lists that cannot be enforced here yet; the command was not run.
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