From: Arjan van de Ven <arjan@infradead.org>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, Jake Edge <jake@lwn.net>,
Eric Paris <eparis@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roland McGrath <roland@redhat.com>,
mingo@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: avoid leaking eip, esp, or wchan to non-privileged processes (fwd)
Date: Sun, 3 May 2009 16:58:17 -0700 [thread overview]
Message-ID: <20090503165817.232c941e@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0905040917240.20251@tundra.namei.org>
On Mon, 4 May 2009 09:27:29 +1000 (EST)
James Morris <jmorris@namei.org> wrote:
> This patch needs some review.
having just gotten back from another trip...
this patch looks relevant, but has a compatibility risk.... Personally
I think it'd be ok, but if things would break we do have some options
that are better than 'do nothing'.
One option to reduce the compatibility risk (as the expense of the
security angle) would be to mask the lower, say 4 to 8 bits of these
variables instead for non-ptrace-capable callers. Other obfuscation
options are obviously also possible.
>
> Having someone specifically responsible for maintaining kernel memory
> protection features would be of immense value. Any takers?
I suppose I could do that.... but would be nice to have a few folks.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-05-03 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 23:27 [PATCH] proc: avoid leaking eip, esp, or wchan to non-privileged processes (fwd) James Morris
2009-05-03 23:58 ` Arjan van de Ven [this message]
2009-05-04 1:11 ` Jake Edge
2009-05-04 14:38 ` Greg KH
2009-05-04 6:09 ` Eric W. Biederman
2009-05-04 13:22 ` Jake Edge
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=20090503165817.232c941e@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eparis@redhat.com \
--cc=jake@lwn.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox