Comment by thomashabets2

Thanks for your work!

As someone else who's banged their head against seccomp and given up (put on hold) I have to say that you're missing one roadblock though. It's not enough that the kernel gets pledge(), but libc needs to cooperate too.

E.g. as I found in https://blog.habets.se/2022/03/seccomp-unsafe-at-any-speed.h... the first printf() you do will do a newfstatat() syscall.

So really there's no way for user space to know which syscalls will be called, just based on common sense. libc can call anything and everything.

And this is why I have less hope for a real pledge() on Linux.