History

Christian Blichmann 75bbd0e1c1 Internal change Only externally visible changes should be a few changed includes as well as some formatting changes. PiperOrigin-RevId: 353226662 Change-Id: Iebf5be13774efcbd94c5d5a17b9b27e47275b229		2021-01-22 06:01:34 -08:00
..
examples	Internal change	2021-01-22 06:01:34 -08:00
ld_preload_example	Move utility code into `sandboxed_api/util`	2021-01-13 09:25:52 -08:00
patches	renamed main project folder	2020-09-28 15:35:51 +00:00
test	Move utility code into `sandboxed_api/util`	2021-01-13 09:25:52 -08:00
.gitignore	Modified sandbox to limit ioctl. Use .value() instead of manually checking .ok().	2020-10-02 15:52:29 +00:00
CMakeLists.txt	Added ld_preload example usage	2020-10-08 10:58:21 +00:00
README.md	added empty line at the end of files (was removed by clang-format)	2020-10-07 14:36:24 +00:00
functions_to_sandbox.txt	renamed main project folder	2020-09-28 15:35:51 +00:00

README.md

libarchive Sandboxed API

Sandboxed version of the libarchive minitar example using Sandboxed API.

Build

mkdir -p build && cd build
cmake .. -G Ninja
cmake --build .

The example binary file can be found at build/examples/sapi_minitar and the unit tests at build/test/sapi_minitar_test.

Patches

The original libarchive code required patching since one of the custom types produced errors with libclang Python byndings. The patches are applied automatically during the build step and they do not modify the functionality of the library. The repository is also fetched automatically.

Examples

In this project, the minitar example is sandboxed. The code is found in the examples directory and is structured as follows:

sapi_minitar_main.cc - main function of the minitar tool. This is mostly similar to the original example.
sapi_minitar.h and sapi_minitar.cc - The two main functions (CreateArchive and ExtractArchive) and other helper functions.
sandbox.h - Custom security policies, depending on the whether the user creates or extracts an archive.

On top of that, unit tests can be found in the test/minitar_test.cc file.

Usage

The unit tests can be executed with ./build/test/sapi_minitar_test.

The sapi_minitar command line tool can be used in the same way as the original example. It is also similar to the tar command, only with fewer options:

./build/examples/sapi_minitar -[options] [-f file] [files]

The available options are:

c - Create archive.
x - Extract archive.
t - Extract archive but only print entries.
p - Preserve.
v - Verbose.
j or y - Compress with BZIP2.
Z - Default compression.
z - Compress with GZIP.

If no compression method is chosen (in the case of archive creation) the files will only be stored.