Settings docs now explain that masked credential files survive a relaxed sandbox filesystem policy while denied ones do not.
What's wrong with this entry?
The settings schema text for skipping filesystem isolation now separates two kinds of credentials.files entries that behave differently under a relaxed filesystem policy.
- Deny entries in credentials.files are dropped and pin the setting to managed settings.
- Mask entries are implemented as sentinel binds, survive the relaxed filesystem policy, and do not pin the setting.
- Env scrubbing is likewise independent of the filesystem policy.
do not pin it — env scrubbing and sentinel binds are independent of the filesystem
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.246
Disabled settings files no longer feed rules into the sandbox
Both mention filesystem credential sandbox
-
v2.1.224
Invalid sandbox credential settings now fail closed instead of being ignored
Both mention credential sandbox