fix(image): pre-grant Local Network Access to the kiosk via Chromium policy#224
Merged
privaloops merged 1 commit intomainfrom Apr 27, 2026
Merged
fix(image): pre-grant Local Network Access to the kiosk via Chromium policy#224privaloops merged 1 commit intomainfrom
privaloops merged 1 commit intomainfrom
Conversation
…policy Chrome 130+ ships a new Local Network Access permission that prompts "<origin> wants to access other apps and services on this device" before letting an HTTPS page fetch any HTTP localhost URL. The kiosk has no pointer or keyboard to dismiss the prompt, so the bridge probe silently failed and launches kept falling back to the embedded TS engine. The flag-based mitigations from #223 don't cover this new permission — it's a separate browser surface, gated by enterprise policy. Drop a managed JSON in /etc/chromium/policies/managed/ that pre-grants both the new (LocalNetworkAccessAllowedForUrls) and legacy (InsecurePrivateNetworkRequestsAllowedForUrls) permission keys for https://frontend.sprixe.dev/*. Chromium picks up the file on launch, no prompt, no flag fragility.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome 130+ ships a new Local Network Access permission that prompts
" wants to access other apps and services on this device"
before letting an HTTPS page fetch any HTTP localhost URL. The kiosk
has no pointer or keyboard to dismiss the prompt, so the bridge probe
silently failed and launches kept falling back to the embedded TS
engine.
The flag-based mitigations from #223 don't cover this new permission
— it's a separate browser surface, gated by enterprise policy. Drop a
managed JSON in /etc/chromium/policies/managed/ that pre-grants both
the new (LocalNetworkAccessAllowedForUrls) and legacy
(InsecurePrivateNetworkRequestsAllowedForUrls) permission keys for
https://frontend.sprixe.dev/*. Chromium picks up the file on launch,
no prompt, no flag fragility.