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
| ||
|
Date: Thu, 4 Apr 2019 09:47:52 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Matthew Garrett <matthewgarrett@...gle.com> cc: jmorris@...ei.org, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, dhowells@...hat.com, linux-api@...r.kernel.org, luto@...nel.org, Matthew Garrett <mjg59@...gle.com>, Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org Subject: Re: [PATCH V32 19/27] x86/mmiotrace: Lock down the testmmiotrace module On Wed, 3 Apr 2019, Matthew Garrett wrote: > From: David Howells <dhowells@...hat.com> > > The testmmiotrace module shouldn't be permitted when the kernel is locked > down as it can be used to arbitrarily read and write MMIO space. This is > a runtime check rather than buildtime in order to allow configurations > where the same kernel may be run in both locked down or permissive modes > depending on local policy. > > Suggested-by: Thomas Gleixner <tglx@...utronix.de> > Signed-off-by: David Howells <dhowells@...hat.com > Signed-off-by: Matthew Garrett <mjg59@...gle.com> Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
Powered by blists - more mailing lists