RustZone: Writing Trusted Applications in Rust
summary
Claim: Rust can replace C for ARM TrustZone trusted apps by eliminating many memory bugs. The project uses bindgen to convert OP-TEE C headers to Rust bindings, builds a Rust library that exports the five TA entry points, cross-compiles to ARM, signs the ELF with the TA signing tool, and runs the demo in QEMU where a simple increment/decrement command works end-to-end. The proof-of-concept builds and executes, but adoption costs and limited Rust expertise remain real obstacles.
AI-written summary · about
chapters (17)
- 0:00Start
- 6:15Use Cases
- 8:47The TrustZone TEE
- 9:41TrustZone in Practice
- 12:42TEE OS Protections
- 14:12Writing (good) C is Hard
- 16:11Example: WideVine Trusted Application
- 18:12Example: Samsung OTP Buffer Overflow
- 19:57What's Rust?
- 21:55Why Rust?
- 25:15Rust / CFFI
- 27:17Learning Rust
- 29:27Get an OS
- 30:08Generate Rust Bindings
- 31:32Write a Rust Library
- 36:41Compile, Link, Sign
- 42:15Conclusions
related talks
34mRusty OP-TEE Trusted Applications
34mWriting an Embedded Operating System in Rust
41mRust Meets Zephyr: Building Safer Embedded Applications
12mLightning Talk: Rust Will Solve All Your Problems, Possibly. Arm’s Journey to Using...
01h 14mRust: A Friendly Introduction- 41mRust Meets Zephyr: Building Safer Embedded Applications
39mSoftware Supply Chain Security with Trusted Execution Environment Provisioning (T...
27mvTZ: Virtualizing ARM TrustZone