News for hackers. Stuff that matters.
Re:Imposing memory security in C [video] by amluto on Thursday February 27, 2025 @03:06PM (#43197911)
I think there’s a sense in which Rust is safer than Fil-C, though: Rust allows abstractions with little to do with memory safety but that still can’t be broken without 'unsafe'. So a struct called EvenNumber can fairly strongly guarantee that it contains an even number.

But Fil-C objects (at least for now?) only seem to allow one single capability type, and that capability grants unrestricted read/write access to the object’s bytes.

I wonder if one could build a handle system in Fil-C that would allow this to be extended. Or if a different variant of a Fil-C-like system could distinguish between pointers with different access levels to an object and could allow only the correct piece of trusted code to increase the permission of a pointer.

Re:Imposing memory security in C [video] by pizlonator on Thursday February 27, 2025 @03:18PM (#43198011)
I’ve thought about adding such things to Fil-C but have held off on going there because it feels like a bridge too far.

What I mean by that is: the memory safety issues of C are a total dumpster fire, while whether a number is even or not (and whether you can prove that) is maybe like icing on the dumpster fire. It just doesn’t matter by comparison.

So I want to decisively fix the memory safety issues and not lose focus.