TPMs and the Linux Kernel: unlocking a better path to hardware security
summary
Proposal adds a new kernel key type that uses TPM2 CreatePrimary in counter mode to derive reproducible per-application keys rather than storing wrapped blobs. Personalization factors include EUID, executable path, inode, or an IMA code checksum; derived keys are returned as a deterministic RNG stream and can be marked non-exportable. Kernel reserves a "kernel" prefix so userland cannot create those primaries. Prototype integrates TPM encrypted sessions, builds as a module, and successfully reproduces keys across boots.
AI-written summary · about
chapters (7)
- 0:00Introduction and TPM overview
- 4:16Problems with TPM usage
- 8:58Linux kernel key retention service
- 15:02Derived keys approach
- 26:31Derived key examples and security
- 31:28RFC and future improvements
- 40:36Q&A and closing remarks
related talks
54mTPMs and the Linux Kernel: unlocking a better path to hardware security
45mTPMs & The Linux Kernel: Unlocking A Better Path To Hardware Security
43mTPMs and the Linux Kernel: unlocking a better path to hardware security
47mTPMs and the Linux Kernel: unlocking a better path to hardware security
42mRecent TPM Security Enhancements to the Linux Kernel
51mApplications of TPM 2.0
23mTPM
39mTPM Is No Silver Bullet: Pitfalls in Embedded Device Security