Hiding Attestation with Linux Keyring in Confidential Virtual Machines
summary
Claims that Linux keyring can hide attestation details for confidential VMs by using the request_key syscall to trigger a userland key provider that performs attestation and fetches secrets from a key broker service. Demonstrates two concrete integrations: cryptsetup fetching disk passphrases via background-check topology and returning JWT attestation tokens via passport topology. Prototype uses confidential-containers KBS client, works in experiments on Intel TDX, and successfully provisions keys into the kernel keyring so legacy apps need no attestation changes.
AI-written summary · about
chapters (10)
- 0:00Confidential computing adoption
- 2:53Talk structure
- 3:58Attestation in confidential VMs
- 8:19Remote attestation topologies
- 13:25Linux keyring deep dive
- 21:37Keyring with attestation for secrets
- 24:29Disk encryption with key broker
- 28:48Attestation token generation
- 31:42Summary and call to action
- 32:47Q&A
related talks
40mDon’t Trust Opaque Clouds, Cryptographically Verify Instead!
29mA Simple Protocol for Remote Attestation of System Integrity
30mTrust No One: Secure Storage With Confidential Containers
27mTrust No One: Bringing Confidential Computing to Containers
24mShrinking The Elephant - A Confidential Computing Attestation Sequel
17mHow to Build a Confidential Attestation Client
43mWhat is Linux kernel keystore and why you should use it in your next app
41mWhat Is Linux Kernel Keystore and Why You Should Use It in Your Next...