Open mrcnski opened 1 year ago
Just to clarify, it should be a matter of calling libc::syscall
with the right parameters and a tiny bit of unsafe
code.
Also, for general usage of seccompiler on modern kernels, getting the available actions shouldn't be a concern, unless the application is using some more recently-added variant, like SECCOMP_RET_USER_NOTIF
.
This could be nevertheless a quality of life wrapper to have in seccompiler, but not super important either
ISSUE
Overview
Hello, I'm writing concerning the following quote from the docs:
Are there any examples of using the second method in practice (
seccomp(SECCOMP_GET_ACTION_AVAIL)
syscall)? It seems likeseccompiler
does not expose any way to do this (would be nice if it did but maybe out of scope?), so it seems like I have to either:libc
to getSECCOMP_GET_ACTION_AVAIL
, orIf you know of any code that already does this it would save me time, and it could be a useful addition to the docs. :)