From: Andrew Morton <akpm@linux-foundation.org>
To: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
jmorris@namei.org, eugeneteo@kernel.org, kees.cook@canonical.com,
mingo@elte.hu, davem@davemloft.net
Subject: Re: [PATCH v2] kptr_restrict for hiding kernel pointers from unprivileged users
Date: Fri, 17 Dec 2010 17:22:31 -0800 [thread overview]
Message-ID: <20101217172231.8842f5cc.akpm@linux-foundation.org> (raw)
In-Reply-To: <1292634759.9764.26.camel@Dan>
On Fri, 17 Dec 2010 20:12:39 -0500
Dan Rosenberg <drosenberg@vsecurity.com> wrote:
> >
> > So what's next? We need to convert 1,000,000 %p callsites to use %pK?
> > That'll be fun. Please consider adding a new checkpatch rule which
> > detects %p and asks people whether they should have used %pK.
>
> The goal of this format specifier is specifically for pointers that are
> exposed to unprivileged users. I agree that hiding all kernel pointers
> would be nice, but I don't expect the angry masses to ever agree to
> that. For now, I'll isolate specific cases, especially in /proc, that
> are clear risks in terms of information leakage. I'll also be skipping
> over pointers written to the syslog, since I think hiding that
> information is dmesg_restrict's job.
Well... some administrators may wish to hide the pointer values even
for privileged callers. That's a pretty trivial add-on for the code
which you have, and means that those admins can also suppress the
pointers for IRQ-time callers. More /proc knobs :)
Then again, perhaps those admins would be OK if we simply disabled
plain old %p everywhere. In which case we're looking at a separate
patch, I suggest.
next prev parent reply other threads:[~2010-12-18 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 0:05 [PATCH v2] kptr_restrict for hiding kernel pointers from unprivileged users Dan Rosenberg
2010-12-11 0:11 ` Kees Cook
2010-12-18 0:44 ` Andrew Morton
2010-12-18 1:12 ` Dan Rosenberg
2010-12-18 1:22 ` Andrew Morton [this message]
2010-12-18 5:22 ` Dan Rosenberg
2010-12-18 0:53 ` Andrew Morton
[not found] <1292385983.9764.5.camel@Dan>
2010-12-15 4:18 ` Eugene Teo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101217172231.8842f5cc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=drosenberg@vsecurity.com \
--cc=eugeneteo@kernel.org \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.