[fuchsia] Add view creation and basic present loop to flatland impl

This CL adds the first set of code to make flatland ozone impl
functional.
- Add ViewProvider hookup for flatland.
- Passes ViewCreation and ViewportCreation tokens to ozone impl
through the new Web.Frame api.
- Connects flatland_window and flatland_surface to scene graph.
- Adds a basic implementation of a main plane allocation and present
loop.

Bug: 1230150
Change-Id: I10a6e062dff86a0c06dddbdec1b1705e447bbc23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3093218
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#934198}
NOKEYCHECK=True
GitOrigin-RevId: 0101823486dd21aa1b98081bce21ea46c0b4ce2f
1 file changed
tree: 5d765e05b559e14fc803faab528f5bd3d693453a
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. COMMON_METADATA
  7. constants.h
  8. DEPS
  9. DIR_METADATA
  10. features.gni
  11. ipc.dict
  12. OWNERS
  13. README.md
  14. sandbox_export.h
README.md

Sandbox Library

This directory contains platform-specific sandboxing libraries. Sandboxing is a technique that can improve the security of an application by separating untrustworthy code (or code that handles untrustworthy data) and restricting its privileges and capabilities.

Each platform relies on the operating system's process primitive to isolate code into distinct security principals, and platform-specific technologies are used to implement the privilege reduction. At a high-level:

  • mac/ uses the Seatbelt sandbox. See the detailed design for more.
  • linux/ uses namespaces and Seccomp-BPF. See the detailed design for more.
  • win/ uses a combination of restricted tokens, distinct job objects, alternate desktops, and integrity levels. See the detailed design for more.

Built on top of the low-level sandboxing library is the //sandbox/policy component, which provides concrete policies and helper utilities for sandboxing specific Chromium processes and services. The core sandbox library cannot depend on the policy component.