Skip to content

Commit a52050b

Browse files
committed
Add post about SOSP.
1 parent 03d3102 commit a52050b

File tree

3 files changed

+47
-0
lines changed

3 files changed

+47
-0
lines changed

_bibliography/publications.bib

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,22 @@
1+
@inproceedings{10.1145/3731569.3764844,
2+
author = {Amar, Saar and Chen, Tony and Chisnall, David and Filardo, Nathaniel Wesley and Laurie, Ben and Lefeuvre, Hugo and Liu, Kunyan and Moore, Simon W. and Norton-Wright, Robert and Seltzer, Margo and Tao, Yucong and Watson, Robert N. M. and Xia, Hongyan},
3+
title = {CHERIoT RTOS: An OS for Fine-Grained Memory-Safe Compartments on Low-Cost Embedded Devices},
4+
year = {2025},
5+
isbn = {9798400718700},
6+
publisher = {Association for Computing Machinery},
7+
address = {New York, NY, USA},
8+
url = {https://doi.org/10.1145/3731569.3764844},
9+
doi = {10.1145/3731569.3764844},
10+
abstract = {Embedded systems do not benefit from strong memory protection, because they are designed to minimize cost. At the same time, there is increasing pressure to connect embedded devices to the internet, where their vulnerable nature makes them routinely subject to compromise. This fundamental tension leads to the current status-quo where exploitable devices put individuals and critical infrastructure at risk.We present the design of a dependable embedded OS where compartmentalization and memory safety are first-class citizens. We co-design the OS with an embedded hardware platform that implements CHERI capabilities at a similar cost profile to existing chips with minimal security. We demonstrate key design benefits: fine-grained fault-tolerant compartments, OS-level support for compartment-interface hardening, and auditing facilities to thwart supply-chain attacks, among others, and show that they come at a memory usage and performance cost that allows their widespread deployment in cheap, resource-constrained devices.},
11+
booktitle = {Proceedings of the ACM SIGOPS 31st Symposium on Operating Systems Principles},
12+
pages = {67–84},
13+
numpages = {18},
14+
location = {Lotte Hotel World, Seoul, Republic of Korea},
15+
series = {SOSP '25},
16+
pdf = {https://dl.acm.org/doi/pdf/10.1145/3731569.3764844}
17+
}
18+
19+
120
@unpublished{riscvsummit2023cheriot,
221
title= {Introduction to CHERIoT},
322
author = {Liu, Kunyan},
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
layout: post
3+
title: "CHERIoT at SOSP 2025"
4+
date: 2025-10-18
5+
categories: rtos publication
6+
author: "David Chisnall"
7+
---
8+
9+
<img alt="Presenting the CHERIoT RTOS paper" width="50%" style="margin-left:auto;margin-right:auto;display:block" src="/images/2025-10-14-sosp.jpg" >
10+
11+
12+
This week, some of the CHERIoT team were at [The 31st Symposium on Operating Systems (SOSP 2025)](https://sigops.org/s/conferences/sosp/2025/index.html) presenting the first paper about the CHERIoT RTOS:
13+
{% cite 10.1145/3731569.3764844 %}.
14+
This paper describes the CHERIoT RTOS and how it builds on the ISA features to deliver fine-grained compartmentalisation, easy programming, and a tiny trusted computing base (TCB).
15+
I also gave a keynote on how CHERI impacts operating system design for the [KISV workshop](https://kisv-workshop.github.io) associated with SOSP.
16+
There were a lot of good discussions, and I hope to see more folks looking at CHERIoT RTOS.
17+
18+
It was interesting to compare our approach with Tock OS, which remains the gold standard for security on non-CHERI embedded devices.
19+
One of the papers in the same session as ours discussed the problems Tock has with untrusted code in userspace violating the Rust invariants.
20+
A lot of these are intrinsic to the problem of interfacing a language that provides (and can therefore depend on) a very rich set of compile-time properties with one that does not guarantee any of these.
21+
It was particularly nice to see that the CHERIoT ISA allows CHERIoT RTOS to enforce some of these properties (such as non-aliasing arising from a no-capture guarantee) *even across trust boundaries*.
22+
That makes me optimistic that CHERIoT RTOS will be one of the best embedded targets for Rust code (more on this coming soon!).
23+
24+
Full citation
25+
-------------
26+
27+
{% bibliography --cited %}
28+

images/2025-10-14-sosp.jpg

242 KB
Loading

0 commit comments

Comments
 (0)