docs(app-vite): audit security guidance#18373
Open
hawkeye64 wants to merge 1 commit into
Open
Conversation
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
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.
What changed
quasar serveexposureWhy
Several security-sensitive examples were incomplete or encouraged unsafe defaults. Most notably, the Electron forwarding example disabled Chromium sandbox protections, the security page omitted current Electron recommendations, the frameless IPC example controlled whichever window happened to be focused, and live-update guidance treated transport and checksums as sufficient without discussing authenticity.
Other cross-mode pages did not clearly distinguish configuration conveniences from security boundaries: public tunnels can expose proxy routes, client environment variables are readable in built applications, extension bridge messages require validation, and signing/update credentials need release-system protections.
Impact
This PR changes guidance and examples without changing generated BEX permissions or application runtime behavior. Existing BEX starter manifests retain their all-sites behavior; users are additionally shown how to narrow permissions when their extension supports known origins.
Validation
quasar dev --helpoutputoxfmt --checkandoxlint --deny-warningsgit diff --check