Two gateway config shapes that used to fail invisibly now warn at boot.
What's wrong with this entry?
The gateway warns about two config shapes that used to fail invisibly.
- If any policy has a
desktopoverlay butlisten.public_urlis unset, it warns that origin pinning cannot be checked, so an origin-pinned value would be dropped by desktops with no sign of it. - If a policy sets
sandbox.network.allowedDomainsto an explicitly empty list, it warns that the derivedcoworkEgressAllowedHostsis not served at all, since desktops treat absent and empty the same.
origin-pin hygiene is skipped at boot
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
Managed-settings review prompt dropped from the main UI
Both mention managed
-
v2.1.242
Startup can wait on a remote managed-settings refresh, with a deadline
Both mention managed
-
v2.1.246
Remote managed settings can defer their consent prompt to the next interactive session
Both mention managed