StarMirror/sandboxed-api
1
0
Fork 0
mirror of https://github.com/google/sandboxed-api.git synced 2024-03-22 13:11:30 +08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #12 from PoignardAzur:patch-1

Browse Source 
PiperOrigin-RevId: 240108388
Change-Id: I4c82e660fb3c7aea9bcc4ba19121d32c7fb4d11a
This commit is contained in:
Christian Blichmann 2019-03-25 13:11:09 +01:00
commit 6679fe8207
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -10,12 +10,12 @@ Copyright 2019 Google LLC
The Sandboxed API project (**SAPI**) aims to make sandboxing of C/C++ libraries The Sandboxed API project (**SAPI**) aims to make sandboxing of C/C++ libraries
less burdensome: after initial setup of security policies and generation of less burdensome: after initial setup of security policies and generation of
library interfaces, an almost-identical stub API is generated (using a library interfaces, an almost-identical stub API is generated (using a
[templated based programming variable hierarchy system](sandboxed_api/docs/variables.md)), [template-based programming variable hierarchy system](sandboxed_api/docs/variables.md)),
transparently forwarding calls using a custom RPC layer to the real library transparently forwarding calls using a custom RPC layer to the real library
running inside a sandboxed environment. running inside a sandboxed environment.
Additionally, each SAPI library utilizes a tightly defined security policy, in Additionally, each SAPI library utilizes a tightly defined security policy, in
contrast to typical sandboxed project, where security policies must cover total contrast to the typical sandboxed project, where security policies must cover the total
syscall/resource footprint of all utilized libraries. syscall/resource footprint of all utilized libraries.