On Fri, 21 Jun 2019, Matthew Garrett wrote: > Minor updates over V33 - security_is_locked_down renamed to > security_locked_down, return value of security_locked_down is returned > in most cases, one unnecessary patch was dropped, couple of minor nits > fixed. Thanks for the respin. We are still not resolved on granularity. Stephen has said he's not sure if a useful policy can be constructed with just confidentiality and integrity settings. I'd be interested to know JJ and Casey's thoughts on lockdown policy flexibility wrt their respective LSMs. These are also "all or nothing" choices which may prevent deployment due to a user needing to allow (presumably controlled or mitigated) exceptions to the policy. -- James Morris <jmorris@xxxxxxxxx>
