Skip to content

add isolation short description #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NiklasMerz wants to merge 1 commit into
base: main
Choose a base branch
from
Open

add isolation short description #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,12 @@ WebView APIs let the host app inject and execute JavaScript and CSS into an site

### Sandbox / process isolation ### {#sandbox-process-isolation}

> [[threat-model-web#sandboxed-web-content-execution-and-rendering|Implementations may also use origin- or site-based isolation strategies so that unrelated web content cannot interfere during normal use or following a compromise, but the exact isolation unit is browser-specific.]]

WebViews inherit the sandbox of their engine, but the isolation unit is effectively chosen by the [=host app=]:
it decides how many WebView instances share a process, and the native bridge gives content running in the sandboxed process a path into app-privileged code.
Neither the user nor the loaded site can tell which isolation guarantees apply.

Issue(#2): How does sandboxing and process isolation work in WebViews?

### Transport: TLS, mixed content ### {#transport}
Expand Down
Loading