linux-kernel - [PATCH] vsprintf: Turn kptr

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110512210028.GA16600@elte.hu>
Date:	Thu, 12 May 2011 23:00:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	torvalds@...ux-foundation.org, eranian@...gle.com, acme@...hat.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH] vsprintf: Turn kptr_restrict off by default

* David Miller <davem@...emloft.net> wrote:

> From: Linus Torvalds <torvalds@...ux-foundation.org>
> Date: Thu, 12 May 2011 13:31:37 -0700
> 
> > That said, I have considered just reverting the thing that makes
> > kptr_restrict be 1 by default. I do like the security implications of
> > restricting visibility into kernel pointers, but I also think that
> > security rules that make the system less usable are dubious. So I
> > dunno.
> 
> We don't have any firewalling or SELINUX rules installed by default, even if 
> those features are enabled in the kernel.  Userspace asks for it.
> 
> Many people would claim that use of such things are "essential" these days.
> 
> I don't see a good reason to handle kptr_restrict any differently.

That's a good argument.

We'll fix the perf bug - i was bitten by another incarnation of it: 'perf top' 
stops showing kernel symbols and it took some time that kptr_restrict was 
turned on by default. I reported it to Arnaldo knows about it but there's no 
fix yet at the moment.

I didnt realize that perf diff got confused by this as well. (but it's logical)

So how about the patch below?

Thanks,

	Ingo

------------------------>
Subject: vsprintf: Turn kptr_restrict off by default

kptr_restrict has been triggering bugs in apps such as perf, and it also makes 
the system less useful by default, so turn it off by default.

This is how we generally handle security features that remove functionality, 
such as firewall code or SELinux - they have to be configured and activated 
from user-space.

Distributions can turn kptr_restrict on again via this line in 
/etc/sysctrl.conf:

kernel.kptr_restrict = 1

( Also mark the variable __read_mostly while at it, as it's typically modified 
  only once per bootup, or not at all. )

Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index bc0ac6b..dfd6019 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -797,7 +797,7 @@ char *uuid_string(char *buf, char *end, const u8 *addr,
 	return string(buf, end, uuid, spec);
 }

-int kptr_restrict = 1;
+int kptr_restrict __read_mostly;

 /*
  * Show a '%p' thing.  A kernel extension is that the '%p' is followed
--
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/