|author||Dan Rosenberg <email@example.com>||2010-11-11 14:05:18 -0800|
|committer||Linus Torvalds <firstname.lastname@example.org>||2010-11-12 07:55:32 -0800|
Restrict unprivileged access to kernel syslog
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. This patch, loosely based on grsecurity's GRKERNSEC_DMESG, creates the dmesg_restrict sysctl. When set to "0", the default, no restrictions are enforced. When set to "1", only users with CAP_SYS_ADMIN can read the kernel syslog via dmesg(8) or other mechanisms. [email@example.com: explain the config option in kernel.txt] Signed-off-by: Dan Rosenberg <firstname.lastname@example.org> Acked-by: Ingo Molnar <email@example.com> Acked-by: Eugene Teo <firstname.lastname@example.org> Acked-by: Kees Cook <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'security/Kconfig')
1 files changed, 12 insertions, 0 deletions
diff --git a/security/Kconfig b/security/Kconfig
index bd72ae62349..e80da955e68 100644
@@ -39,6 +39,18 @@ config KEYS_DEBUG_PROC_KEYS
If you are unsure as to whether this is required, answer N.
+ bool "Restrict unprivileged access to the kernel syslog"
+ default n
+ This enforces restrictions on unprivileged users reading the kernel
+ syslog via dmesg(8).
+ If this option is not selected, no restrictions will be enforced
+ unless the dmesg_restrict sysctl is explicitly set to (1).
+ If you are unsure how to answer this question, answer N.
bool "Enable different security models"
depends on SYSFS