OP-TEE: When Linux Loses Control
summary
OP-TEE runs as a Trusted Execution Environment on ARM using SMC to isolate a secure world and expose services to Linux via an optidriver shim. The implementation adds physical-clock bindings, peripheral status masks and a "buzz/secure controller" model to gate clocks, power and reset, and it exposes secure RNG and timer services to Linux. Several patches are merged and others are still in review; it runs on multiple SoCs but requires per‑platform device-tree and platform‑code work.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:58What is OP-TEE and architecture
- 10:45Secure peripherals importance
- 18:11Hardware isolation and security
- 27:44Clock management and bindings
- 33:09Linux driver architecture
- 37:21Security features and contributions
related talks
11mOP-TEE open-source security for the mass-market
41mOP-TEE - Using TrustZone to Protect Our Own Secrets
34mA Journey To the Secure World of OPTEE From the Non-secure World of Linux
48mOP-TEE: Using the ARM Trust-Zone to Control Tamper Resistant Processors
10mLightning Talk: A Trusted OS for RISC-V ? OP-TEE is a Candidate
17mEnhancing OP-TEE for RISC-V: Leveraging IOPMP and Enabling RTOS Integration
24mSecure boot, TEEs, different OSes and more
48mKernel TEE Subsystem Evolution