Script Integrity
summary
Linux 6.14 adds a concrete kernel capability to control script execution: a new execveat(2) AT_EXEC_CHECK flag plus prctl successors to O_MAYEXEC, and two new securebits: enforce / deny-interactive flags to incrementally apply policies. Enforcement uses file-descriptor checks to avoid TOCTOU, integrates with IMA/LSMs, and requires “enlightened” interpreters (Python, Bash, Ruby) to open-then-verify scripts; a small test wrapper in the kernel tree demonstrates the feature and the kernel-side implementation is merged.
AI-written summary · about
chapters (12)
- 0:00Script integrity introduction
- 1:30Why scripts need integrity
- 3:17Kernel and script execution
- 7:19Enforcing execution policies
- 10:17Handling libraries and trusted code
- 13:51Script interpreter considerations
- 14:34History of the solution
- 16:24Configuring restrictions incrementally
- 17:31Next steps and docs
- 18:13Q&A on file descriptors
- 19:40Q&A on interpreter pitfalls
- 21:29Q&A on user space support
related talks
46mControlling Script Execution
26mA Practical Approach to Control Unauthorized Execution of Interpreters
43mIntegrity Policy Enforcement: Full System Integrity Verification
26mIntegrity
30mLinux Kernel Security Contributions by ANSSI
47mApplication Whitelisting
19mSubsystem Update: Linux Integrity Status Update
36mSeccomp For Developers - Writing More Secure Applications
