Axel Rasmussen <axelrasmussen@xxxxxxxxxx> writes: > I think for any approach involving syscalls, we need to be able to > control access to who can call a syscall. Maybe there's another way > I'm not aware of, but I think today the only mechanism to do this is > capabilities. I proposed adding a CAP_USERFAULTFD for this purpose, > but that approach was rejected [1]. So, I'm not sure of another way > besides using a device node. I take it there's a reason why this can't be done with a security module - either a custom module or a policy in one of the existing modules? That sort of access control is just what security modules are supposed to be for, after all. Thanks, jon
