Messages in this thread | | | Date | Tue, 9 Apr 2013 09:33:08 -0700 | Subject | Re: [PATCH v2] kmsg: Honor dmesg_restrict sysctl on /dev/kmsg | From | Kees Cook <> |
| |
On Tue, Apr 9, 2013 at 8:48 AM, Josh Boyer <jwboyer@redhat.com> wrote: > The dmesg_restrict sysctl currently covers the syslog method for access > dmesg, however /dev/kmsg isn't covered by the same protections. Most > people haven't noticed because util-linux dmesg(1) defaults to using the > syslog method for access in older versions. With util-linux dmesg(1) > defaults to reading directly from /dev/kmsg. > > Fix this by reworking all of the access methods to use the > check_syslog_permissions function and adding checks to devkmsg_open and > devkmsg_read. > > This fixes https://bugzilla.redhat.com/show_bug.cgi?id=903192 > > Reported-by: Christian Kujau <lists@nerdbynature.de> > CC: stable@vger.kernel.org > Signed-off-by: Eric Paris <eparis@redhat.com> > Signed-off-by: Josh Boyer <jwboyer@redhat.com>
Thanks!
Acked-by: Kees Cook <keescook@chromium.org>
-- Kees Cook Chrome OS Security
| |