Messages in this thread | | | Date | Tue, 9 Nov 2010 12:06:49 +0000 | From | Alan Cox <> | Subject | Re: [PATCH] Restrict unprivileged access to kernel syslog |
| |
On Mon, 08 Nov 2010 22:28:58 -0500 Dan Rosenberg <drosenberg@vsecurity.com> wrote:
> The kernel syslog contains debugging information that is often useful > during exploitation of other vulnerabilities, such as kernel heap > addresses. Rather than futilely attempt to sanitize hundreds (or > thousands) of printk statements and simultaneously cripple useful > debugging functionality, it is far simpler to create an option that > prevents unprivileged users from reading the syslog.
Except for anything that appears on the screen - which is remotely readable via the screen access APIs. Looks sane to me (pointless but sane) and the checks match the ones needed to redirect the console so you need CAP_SYS_ADMIN either way.
| |