Rusty OP-TEE Trusted Applications
summary
OP-TEE Trusted Applications get a Rust toolchain path that uses no_std support, the OP-TEE C libraries and three Rust crates (opt, opt_build and a protocol crate) to produce signed TA binaries that hit performance parity with C and shrink binaries by 70–80 KB. Builds cross-compile for aarch64, run on kamu emulation, accept standard GP-style UUID commands, and suggest next steps: stable toolchain, standardized Rust TA APIs and pseudo trusted applications as the migration starting point.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:03What is OP-TEE
- 6:00OP-TEE architecture
- 9:56Communication stack
- 10:19Rust for Trusted Apps
- 13:56Custom Rust targets challenges
- 16:47no_std for OP-TEE
- 19:15Rust TA directory structure
- 21:01Rust client application
- 23:13Protocol crate for commands
- 24:17TA entry points in Rust
- 26:50Building and signing Rust TAs
- 28:36Limitations and future work
- 32:11Q&A
related talks
48mRustZone: Writing Trusted Applications in Rust
11mOP-TEE open-source security for the mass-market
41mOP-TEE - Using TrustZone to Protect Our Own Secrets
10mLightning Talk: A Trusted OS for RISC-V ? OP-TEE is a Candidate
50mUsing OP-TEE as a Cryptography Engine
40mOP-TEE: When Linux Loses Control
09mDemo: Facilitating Trusted Application Migration to RISC-V
39mSoftware Supply Chain Security with Trusted Execution Environment Provisioning (T...