Memory safe Linux demo

Awesome! I wonder if it's easy for you to compile a vulnerable version of some software with regular C, run an exploit agaist it, get an RCE or so, and then do the same but compile that software with FilC first. This way you show the practical purpose of your memory safety

Like this?

Yeah right! Missed that

Nice work 💪 interesting to see it action 🤩 what would you estimate on average in % slower than C and memory usage compared to C? This could initially be very interesting for security critical systems.

It’s measurably slower and uses measurably more memory. But like my demo shows, you won’t notice it as a user

@per_arneng Are there any user domains where it would be noticeable assuming FilC would become more widespread?

@per_arneng Yeah. Games for example

Is this also memory safe with things like data races?

@xslendix Yes

Very nice demo, and this looks great. I’m curious what the output of that stack traces is when you don’t include debug information, or does fil-c always embed debug information?

The file name and line number become “<somewhere>” Inline frames are collapsed. But at least currently, I still keep function names. I might add an option to strip those (folks wanting minimum footprint will appreciate that)

I do have a concern though that it would open the executable up to easier reverse engineering. But that is a different issue and the goal is memory safety.

Very cool!

> mfw I heard SystemV. > mfw I have no face

Awesome

@awesomekling I'm gonna be the guy that ignores all this incredible work that clearly took an immense amount of time to create and only comment on the squeaky chair.

why does rust even exist XD

@chromatic_x @xorloser

Probably would be even more useful to have a fil-c user space in a docker container

What would be the value of having the memory safe stuff inside a container? I imagine you might want the opposite: - Your host OS has a memory safe userland - If you want to run unsafe code (for perf reasons) you do it in a container

To make it easier to cross compile stuff when you need access to a bunch of system packages through pkg-config

Excellent work and thanks for sharing! Any chance you wanna take on another DE / composter and push further into userland? If that is a silly question, let me rephrase: what is the next step?

Next step is web browser

@awesomekling Great work 👏

Awesome background!! but, with all seriousness thanks for the rundown, really provides very useful context for understanding.

👀

Video quality too low.

This is great! Is there a write up somewhere describing how invisicaps are actually implemented? IIUC, they are created/used at runtime, not compile time.

Would you consider uploading this to YouTube as well? (easier to share a "here, watch this" link with folks) 🙂

@ooPo