Integrity Protection and Access Control - Who Do You Trust?
summary
Describes a small LSM called Path Trust that ties elevated capabilities and SEAndroid types to partition integrity by checking DM‑Verity at mount time, exposing a device node to veto execs from untrusted user-data. Version one prevents privileged binaries on user-data from running but does not stop access to their files. Covers ext4 per-file encryption gaps, a prototype authenticated-encryption patch with per-block keys, and practical pitfalls: relabeling, metadata protection, and crash-consistency for auth tags.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:29What can an attacker do
- 1:44DMCrypt
- 3:53PathTrust
- 4:42SuperUser
- 6:45How does it work
- 8:55The pitfalls
- 11:41Discussion questions
- 14:41Comments
- 19:46Integrity and Linux
- 22:49Should Encryption require Integrity
- 26:01Linux Integrity Protection
- 28:21VM Integrity Protection
- 31:24Extended Attributes
related talks
43mIntegrity Policy Enforcement: Full System Integrity Verification
34mAuthenticated and Encrypted Storage on Embedded Linux
34mTying EVM into LSM Policy
45mNavigating Security Tradeoffs in Embedded Linux Systems
28mAndroid boot verification to ensure integrity of OS and parti…
41mProtecting Your System from the Scum of the Universe
36mOverview and Recent Developments: Linux Integrity
44mCan You Trust Me Now? An Exploration Into the Mobile Threat Landscape