From ffd40549b94960ab72981e4383bcf98d0531d295 Mon Sep 17 00:00:00 2001 From: Shravan Narayan Date: Tue, 6 Feb 2024 14:22:27 -0600 Subject: [PATCH] Readme - Add blurb about what RLBox does --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1e3ab1d..cc37f17 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ This wasm2c/wasm integration with RLBox depends on 3 external tools/libraries th 1. [A clang compiler with support for WASM/WASI backend, and the WASI sysroot](https://github.com/CraneStation/wasi-sdk). This allows you to compile C/C++ code to WASM modules usable outside of web browsers (in desktop applications). 2. [The wasm2c compiler](https://github.com/WebAssembly/wabt/) that compiles the produced WASM/WASI module to C code that you can compile with a standard C compiler. -3. [The RLBox APIs]((https://github.com/PLSysSec/rlbox_api_cpp17)) - A set of APIs that allow easy use of sandboxed libraries. +3. [The RLBox APIs]((https://github.com/PLSysSec/rlbox_api_cpp17)) - A set of APIs that allow easy use of sandboxed code. It handles ABI differences between sandboxed (Wasm) code and native code, and ensures that you include data sanitization checks on untrusted data returned by the sandboxed C code. In the below steps, you can either use the automatically pulled in versions as described below, or download the tools yourself.