On Fri, 8 Dec 2017, Sargun Dhillon wrote: > The purpose of this is similar to the purpose of something like > iptables -L -n. With the proliferation of LSMs, it's going to > be more important to have a way to understand what's going on.
The difference with iptables being that it's an application on top of the netfilter hooks, with strongly defined behavioral semantics for matches and targets, while their configuration is the security policy. LSM is more like the raw netfilter layer, and I don't think you can make a lot of sense from a list of just which hooks are active. You need semantic knowledge of how those hooks are configured, i.e. security policy. I suggest dropping this part for now at least, and perhaps think about building an API on top of this feature with strongly defined semantics (e.g. something like iptables on top of netfilter). - James -- James Morris <[email protected]>
