Allow adding syscalls by group names #18
Cargando…
x
Referencia en una nueva incidencia
Block a user
No se ha proporcionado una descripción.
Eliminar rama "%!s() "
Eliminar una rama es permanente. Aunque la rama eliminada puede continuar existiendo durante un corto tiempo antes de que sea eliminada, en la mayoría de los casos NO PUEDE deshacerse. ¿Continuar?
If you add "open", there is a chance you also want to block "openat"...
So make this easy by allow adding system call by group names to the policy.
Also, maybe take some inspiration from pledge().
If there was a kernel update, but no qssb.h update or code is using an outdated verison, new syscalls could have been added that are not in any group yet.
Thus, we may habe to auto blacklist all those that we do not know.
Alternatively, adding syscalls by groups should only be allowed for whitelisting?