-
Notifications
You must be signed in to change notification settings - Fork 153
Demo videos 2019
Here are two short demo videos of an early (late 2019) build of core Enarx functionality in action.
They show the same example being run on two different underlying physical TEE technologies, AMD SEV and Intel SGX.
In this first example, you can see a Keep being initiated using AMD SEV and executing a simple addition.
Want to try it out for yourself? Make sure you've got everything you need before you begin:
- An AMD processor with SEV capabilities (EPYC)
- A Linux kernel with
CONFIG_KVM_AMD_SEVenabled (set to 'y') with the appropriate kernel command line parameters set:mem_encrypt=on kvm_amd.sev=1- NOTE: The above requirements are out of scope for this document. Please refer to the following resources and/or your favorite internet search engine to get started.
- How do I build the Linux kernel?
- How do I set kernel command line parameters?
- An Enarx development environment
- The
wasm32-unknown-unknownRust toolchain target
$ rustup target add wasm32-unknown-unknown- The
cmakepackage must be installed to build the demo
- Clone the demo repository:
$ git clone https://github.com/enarx/demo.git- Enter the cloned repository and build the project:
$ cd demo
$ cargo buildOnce built, the demo can be ran like so:
$ cargo run --bin demo 3 4Alternatively:
$ ./target/debug/demo 3 4In this second example, the same thing is done using Intel SGX.
For more information about Enarx, please refer to the introduction or the FAQ
For more information about Enarx components, please refer to the Enarx components page.
For more information about TEEs, please refer to the TEEs page.
- Introduction
- Demo videos
- FAQ
- The problem Enarx is trying to solve, in one picture
- Design principles
- Threat Model
- Runtime trust architecture
- Enarx In-Depth Presentation Slides
- Enarx runtime
- Enarx components
- Enarx process flow
- Enarx Syscall Proxy
- Enarx syscall: get_attestation
- Trusted Execution Environments (TEEs)
- WebAssembly (Wasm)