News for hackers. Stuff that matters.
Re:Unsafe at any clock speed: Linux kernel security needs a ... by eugeneionesco on Tuesday September 27, 2016 @08:40PM (#12594553)
You can't this seriously since it does not mention grsecurity.

No need to "rethink" kernel security, just use grsecurity.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by viraptor on Tuesday September 27, 2016 @09:14PM (#12594713)
They do mention it, just not by name. Kees Cook and the Kernel Self Protection Project is basically trying to move some protections that exist in grsec into mainline kernel. (since grsec as a whole will never get accepted)
Re:Unsafe at any clock speed: Linux kernel security needs a ... by micaksica on Wednesday September 28, 2016 @01:34AM (#12595638)
And a 2009 LWN post as to why grsec won't be accepted: https://lwn.net/Articles/313621/
Re:Unsafe at any clock speed: Linux kernel security needs a ... by jaimex2 on Wednesday September 28, 2016 @08:13AM (#12597050)
Is grsecurity the same as SELinux?
Re:Unsafe at any clock speed: Linux kernel security needs a ... by na85 on Tuesday September 27, 2016 @08:58PM (#12594641)
Yes, it's always bad to go over things with a critical eye, looking for a better approach that might exist.

Better to just stick with the status quo and not ask too many questions.

Re:Unsafe at any clock speed: Linux kernel security needs a ... by drvdevd on Tuesday September 27, 2016 @09:09PM (#12594685)
Actually, it does seem odd that grsecurity wasn't mentioned. It's the first thing that comes to mind when I think of "killing entire classes of bugs" in the Linux Kernel. Many of the "safety" features we have now in most operating systems started there.. ASLR for example: https://en.wikipedia.org/wiki/Address_space_layout_randomiza...