Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-23 Thread Kees Cook
On Tue, Oct 23, 2018 at 9:48 AM, Casey Schaufler wrote: > On 10/12/2018 12:01 PM, Kees Cook wrote: >> On Friday, October 12, 2018 3:19 AM, John Johansen >> wrote: >>> It isn't perfect but it manages consistency across distros as best as >>> can be achieved atm. >> Yeah, this is why I'm okay with

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-23 Thread Kees Cook
On Tue, Oct 23, 2018 at 9:48 AM, Casey Schaufler wrote: > On 10/12/2018 12:01 PM, Kees Cook wrote: >> On Friday, October 12, 2018 3:19 AM, John Johansen >> wrote: >>> It isn't perfect but it manages consistency across distros as best as >>> can be achieved atm. >> Yeah, this is why I'm okay with

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-12 Thread John Johansen
On 10/12/2018 04:31 AM, Jordan Glover wrote: > ‐‐‐ Original Message ‐‐‐ > On Friday, October 12, 2018 2:26 AM, John Johansen > wrote: > >> On 10/11/2018 04:53 PM, Jordan Glover wrote: >> >>> ‐‐‐ Original Message ‐‐‐ >>> On Friday, October 12, 2018 1:09 AM, Kees Cook

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-12 Thread John Johansen
On 10/12/2018 04:31 AM, Jordan Glover wrote: > ‐‐‐ Original Message ‐‐‐ > On Friday, October 12, 2018 2:26 AM, John Johansen > wrote: > >> On 10/11/2018 04:53 PM, Jordan Glover wrote: >> >>> ‐‐‐ Original Message ‐‐‐ >>> On Friday, October 12, 2018 1:09 AM, Kees Cook

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-11 Thread Kees Cook
On Wed, Oct 10, 2018 at 8:45 PM, James Morris wrote: > On Wed, 10 Oct 2018, Kees Cook wrote: > >> v5: >> - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling >> - dropped various Reviewed-bys due to rather large refactoring > > Patches 1-10 applied to >

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-11 Thread Kees Cook
On Wed, Oct 10, 2018 at 8:45 PM, James Morris wrote: > On Wed, 10 Oct 2018, Kees Cook wrote: > >> v5: >> - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling >> - dropped various Reviewed-bys due to rather large refactoring > > Patches 1-10 applied to >

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-10 Thread James Morris
On Wed, 10 Oct 2018, Kees Cook wrote: > v5: > - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling > - dropped various Reviewed-bys due to rather large refactoring Patches 1-10 applied to git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general

Re: [PATCH security-next v5 00/30] LSM: Explict ordering

2018-10-10 Thread James Morris
On Wed, 10 Oct 2018, Kees Cook wrote: > v5: > - redesigned to use CONFIG_LSM= and lsm= for both ordering and enabling > - dropped various Reviewed-bys due to rather large refactoring Patches 1-10 applied to git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general