| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAGXu5jJUZoKksT3AY3fF9Nt66FL+6mDbmUnYVGVChpeV=UT_2g@mail.gmail.com> Date: Tue, 1 Nov 2011 14:05:13 -0700 From: Kees Cook <keescook@...omium.org> To: James Morris <jmorris@...ei.org> Cc: linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org Subject: Re: [PATCH v6 0/3] security: Yama LSM On Tue, Nov 1, 2011 at 1:45 PM, James Morris <jmorris@...ei.org> wrote: > On Wed, 26 Oct 2011, Kees Cook wrote: > > > As discussed at the Linux Security Summit, I'm resubmitting this > > code. As an LSM, it has coherent policy around expanding specific DAC > > behaviors. There is no need for it to be a full-blown MAC, since it is > > not intended to be one, but rather to be a simplified expansion to DAC, > > with system-wide knobs. See the specific patches for details... > > Yes, there was a strong consensus (unanimous I believe) at the security > summit on incorporating the Yama LSM as a container for generally useful > miscellaneous security hardening features that don't belong elsewhere. > > This means that LSM is no longer 'officially' only for access control > mechanisms. That would be very welcome. > We probably need to flesh out criteria for inclusion in Yama and document > it. What's the best way for me to help with that documentation? Thanks, -Kees -- Kees Cook ChromeOS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists