Static Information Flow Control Made Simple
summary
Proposes a rule-based IFC that unifies confidentiality and integrity by declaring concrete flows between modules, using overrides via lexical scope to allow temporary exceptions and an allow coercion to hand a value to untracked code; formalization embeds into Rust’s type system and a progress/preservation proof is in progress. Demonstrated on TLS private‑key management in Rocket and Conduit (Rust): keys get confined into a TLS listener rather than leaked to locals, no user studies yet but the prototype and case studies validate the approach.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:55Flow Diagram
- 8:04Application
- 9:47Example
- 12:10Case Study
- 19:49Allow Construct
- 23:02User Settings
- 23:30Progressive Evaluation
- 24:06Consistency
- 26:48Conclusion
related talks
18mCocoon: Static Information Flow Control in Rust
15mStructural Information Flow: A Fresh Look at Types for Non-Interference
26mInformation Flow Confidentiality and Integrity on a Rocket RISC-V SoC
01h 46mA little Introduction to Control Flow Integrity
15mCarapace: Static–Dynamic Information Flow Control in Rust
15mLiquid Information Flow Control
24mRFC: Secret types in Rust
44mLinux Kernel Control-Flow Integrity Sup...