|
| 1 | ++++ |
| 2 | +title = "Verifying VTock" |
| 3 | +date = 2024-02-24 |
| 4 | ++++ |
| 5 | + |
| 6 | +Tock is a modern operating system designed to safely run multiple distrustful |
| 7 | +applications on millions of embedded devices. While Tock is written in Rust, a |
| 8 | +type and memory safe language, low-level hardware abstractions remain |
| 9 | +fundamentally unsafe. Relying solely on language and hardware safety features is |
| 10 | +not enough to prevent bugs that compromise one of Tock's core guarantees: |
| 11 | +process isolation. In particular, isolation has been violated by bugs in |
| 12 | +interrupt handling, context switching, and hardware configuration code. To |
| 13 | +address these challenges, we are building VTock, a formally verified fork of |
| 14 | +Tock that uses Flux, an automatic Rust verifier, to prove the correctness of |
| 15 | +security-critical properties. In this talk, I will give an overview of our |
| 16 | +verification efforts along with some of the challenges we have faced verifying |
| 17 | +production Rust code. |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +About the speaker: Vivien Rindisbacher |
| 22 | + |
| 23 | +Hi! I'm a PhD Student in the Programming Systems Group at the University of |
| 24 | +California San Diego (UCSD). My research focuses on lightweight verification of |
| 25 | +Rust code using tools like Flux. Before joining UCSD, I worked as a Software |
| 26 | +Engineer at Dimensional Fund Advisors and completed my undergraduate degree at |
| 27 | +Boston University. Feel free to check out my website for more details: |
| 28 | +https://www.vivienrindisbacher.com/ |
| 29 | + |
| 30 | +**Meeting Link**: [Zoom Link](https://ethz.zoom.us/j/62101458314) |
0 commit comments