Policy helper paths must be fully normalized, and Windows needs a drive or UNC path.
What's wrong with this entry?
The managed-settings policy helper path check now rejects . and .. segments, doubled or trailing separators, and on Windows requires a drive-qualified or UNC path with no device-namespace prefix. This is on top of the existing absolute-path and .exe checks, and failures return code: "bad_path".
- The check also moved inside the runner, so it applies at the point the helper is invoked.
path must be in normalized form (no "." or ".." segments, no doubled or trailing separators)
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.228
Managed settings accept per-OS
policyHelpersBoth mention policy helper managed
-
v2.1.228
New
policyHelpersmanaged-settings key for per-OS policy helper executablesBoth mention policy helper managed
-
v2.1.235
Policy helpers can be delivered by remote managed settings, after explicit approval
Both mention policy helper managed