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: Sun, 29 Nov 2015 09:08:53 +0100 From: Ingo Molnar <mingo@...nel.org> To: PaX Team <pageexec@...email.hu> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, kernel-hardening@...ts.openwall.com, Mathias Krause <minipli@...glemail.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Kees Cook <keescook@...omium.org>, Andy Lutomirski <luto@...capital.net>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, x86-ml <x86@...nel.org>, Arnd Bergmann <arnd@...db.de>, Michael Ellerman <mpe@...erman.id.au>, linux-arch@...r.kernel.org, Emese Revfy <re.emese@...il.com> Subject: Re: [kernel-hardening] [PATCH 0/2] introduce post-init read-only memory * PaX Team <pageexec@...email.hu> wrote: > i don't see the compile time vs. runtime detection as 'competing' approaches, > both have their own role. [...] That's true - but only as long as 'this can be solved in tooling!' is not used as an excuse to oppose the runtime solution and we end up doing neither. Thanks, Ingo -- 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