Hacker News new | past | comments | ask | show | jobs | submit login

C can be memory safe, we only need to turn these features on. Oh, by the way, these features don’t exist.





10K memory safe packages (so far): https://www.cheribsd.org

And it only requires massive hardware changes and overhead that no one has put into production. Morello is still a research project afaik.

CHERI-RISC-V is being standardised [1], Codasip is working on a commercial implementation of CHERI-RISC-V [2], and lowRISC is working on the Sonata project [3] implementing CHERIoT.

The Early performance results from the prototype Morello microarchitecture report [4] predicts the overhead between 1.8% and 3.0%. We don’t know what that overhead would be in production until such a commercial implementation is delivered but we have enough evidence it is worth the effort with the current estimates and given that CHERI can deterministically prevent around 2/3 of memory-safety-related vulnerabilities [5], not to mention benefits of mitigating future unknown vulnerabilities with compartmentalisation.

[1] https://github.com/riscv/riscv-cheri

[2] https://codasip.com/solutions/riscv-processor-safety-securit...

[3] https://www.sunburst-project.org/

[4] https://ctsrd-cheri.github.io/morello-early-performance-resu...

[5] https://msrc.microsoft.com/blog/2020/10/security-analysis-of...


While CHERI isn't, SPARC ADI, and ARM MTE are.


Circle is C++ not C and its Safety proposals are mostly just ideas at the moment.

More than ideas I think, and any safety proposal based on pointer annotations will carry a much higher burden than converting to C++ anyway.

Fil-C is more than just ideas though.


Don't worry, they said it's relatively easy to add!

Everything is relatively easy, relative to something out there.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: