A policyHelper only runs if it comes from admin settings; anywhere else it is ignored.
What's wrong with this entry?
A policyHelper configured through any non-admin settings source is now logged and dropped instead of being executed.
policyHelper ignored: delivered via non-admin source
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.235
Wider environment scrubbing before a policy helper is spawned
Both mention policy helper
-
v2.1.235
A remote-armed policy helper's output is discarded if it is revoked mid-run
Both mention policy helper
-
v2.1.235
Stricter rules for policy helpers arriving over remote settings
Both mention policy helper