On Thu, 24 May 2018, Eric W. Biederman wrote: > Below is where I suggest you start on sorting out these security hooks. > - Adding a security_kernel_arg to catch when you want to allow/deny the > use of an argument to a syscall. What security_kernel_file_read and > security_kernel_file_post_read have been abused for. NAK. This abstraction is too semantically weak. LSM hooks need to map to stronger semantics so we can reason about what the hook and the policy is supposed to be mediating. -- James Morris <jmorris@xxxxxxxxx>
