3 ms·
Perhaps one day the OpenBSD folks will figure out how to completely prevent user programs from making syscalls. It seems they are mostly there but still not qui
by Joker_vD 2y ago
Perhaps one day the OpenBSD folks will figure out how to completely prevent user programs from making syscalls. It seems they are mostly there but still not quite. Please don't mention WASM in your replies.
- ori_b 2y agoIt's rather hard to do anything useful if you disable i/o.
- Joker_vD 2y agoPrecisely! And yet they make it really hard for my shellcode to do anything useful for some reason, ugh.
- ori_b 2y agoSince the only way a program like that would be interacting with the environment via a side channel, it'd be equivalent to not running the code at all. As a result, you can disable all syscalls for your program with one simple request: 'exit()'
- j16sdiz 2y agoPrinting hello world is a syscall - you need that to write to STDOUT . There are alternative to syscall. For example, writing to shared memory. Shared memory as IPC is hard. And you need some syscall to set the memory up.. .
- yjftsjthsd-h 2y agoAre you referring to their only allowing syscalls from libc? Because AFAIK that's fully functional already? Or if you're trying to solve a problem, what are you doing that pledge() doesn't cover? For that matter WASM.... would do that, so why not use it?