Hacker News Reader

Memory-safe languages aren't enough to protect you from incorrect syscalls/kernel bugs, bad JIT code, or attacker controlled processes writing into your memory. Secure hardware can help with all those things.

CHERIoT somewhat anticipated this perspective.

https://cheriot.org/cheri/myths/2024/08/28/cheri-myths-safe-...

The entire premise seems to be that if you are stuck using not Rust in some way then CHERI helps. How is my comment not correct then? This is a bandaid to help poorly written code handle memory faults with hardware exceptions. MMU and MPUs do this as well without the cost of fat pointers which is non negligible. Rust does this with the compiler before the firmware even runs.

Is it neat? Sure. Is it practical and useful? I’m skeptical.

You weren't fooled into believing that Rust = computer security, were you?

Google sure seems to think it’s solved and prevented many exploits. Do you have similar credentials to back your statement suggesting Rust doesn’t solve a category of security issues? The same kind this hardware extension is looking to solve?