A control message can suspend sandbox auto-allow, making the session behave like plan mode for permissions.
What's wrong with this entry?
A new application state, set by an incoming control message rather than any local flag, marks sandbox auto-allow as suspended. While set, permission checks treat the session like plan mode, so commands inside the sandbox stop being auto-allowed without the permission mode itself changing.
sandbox_auto_allow_suspended
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