The Case for Memory Safe Roadmaps
1–10 of 427 posts
Re: The Case for Memory Safe Roadmaps
#2At least my usecase has C completely disconnected from the internet.
I have no idea how this is going to work at the OS level.
Re: The Case for Memory Safe Roadmaps
#3At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
What is the "this" referred to here?
Re: The Case for Memory Safe Roadmaps
#4At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
Based on early days of Rust in the Linux kernel, the segmentation of safe and unsafe code can significantly reduce the surface area within a kernel.
Re: The Case for Memory Safe Roadmaps
#5Re: The Case for Memory Safe Roadmaps
#6Their "Appendix: Memory Safe Languages" lists:
C#, Go, Java, Python, Rust & Swift
Re: The Case for Memory Safe Roadmaps
#7At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
Based on early days of Rust in the Linux kernel, the segmentation of safe and unsafe code can significantly reduce the surface area within a kernel.
I mean it's obvious why it works. The less code that has to be heavily scrutinized for memory issues, the more the few people that can scrutinize such code can focus on the parts that still need that level of scrutiny.
Re: The Case for Memory Safe Roadmaps
#8At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
Based on early days of Rust in the Linux kernel, the segmentation of safe and unsafe code can significantly reduce the surface area within a kernel.
Do you rewrite the Linux kernel as-is in Rust or try something new? Would/should a Linux in Rust look the same?
Re: The Case for Memory Safe Roadmaps
#9At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
Based on early days of Rust in the Linux kernel, the segmentation of safe and unsafe code can significantly reduce the surface area within a kernel.
I realize this is beating a dead horse, but it really is a shame that microkernels didn't win for human-facing Unix systems. This issue was recognized and basically solved decades ago, and we're still almost there.
Re: The Case for Memory Safe Roadmaps
#10Encouraging. I hope the increasing drumbeat of awareness and advocacy around this reaches a critical mass soon. I'm not naive enough to think it will solve all security problems, but it will reduce the attack surface so, so much.