From: Arjan van de Ven <arjan@infradead.org>
To: James Morris <jmorris@namei.org>
Cc: Theodore Tso <tytso@mit.edu>,
David Wagner <daw-news@cs.berkeley.edu>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: Security: information leaks in /proc enable keystroke recovery
Date: Sun, 16 Aug 2009 20:16:06 -0700 [thread overview]
Message-ID: <20090816201606.6e96efc8@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0908171237050.30748@tundra.namei.org>
On Mon, 17 Aug 2009 12:45:45 +1000 (EST)
James Morris <jmorris@namei.org> wrote:
> On Sun, 16 Aug 2009, Theodore Tso wrote:
>
> > On Mon, Aug 17, 2009 at 12:31:38AM +0000, David Wagner wrote:
> > >
> > > OK. What about this:
> > >
> > > (a) Remove ESP and EIP from /proc/$pid/stat{,us} entirely. Put
> > > them in some other file that is only readable by root and by the
> > > owner of the process, but is not world-readable. We know that
> > > ESP and EIP can be used for keystroke recovery, and they are not
> > > usually used by administrators, so the first step is to lock them
> > > down tightly: there is no downside.
> >
> > Agreed.
>
> It might be best to require a capability for this if not root.
>
> The candidates seem to be CAP_SYS_ADMIN and CAP_SYS_PTRACE.
I would suggest we just use the "can ptrace" permission function
altogether... (after all, if you can ptrace an app you already own all
its keys)
--
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-08-17 3:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 22:21 Security: information leaks in /proc enable keystroke recovery David Wagner
2009-08-15 23:25 ` Oliver Pinter
2009-08-16 20:06 ` Robert Watson
2009-08-16 21:09 ` David Wagner
2009-08-16 23:25 ` Robert N. M. Watson
2009-08-17 0:58 ` David Wagner
2009-08-17 10:11 ` Robert Watson
2009-08-19 1:57 ` Dag-Erling Smørgrav
2009-08-16 0:33 ` Theodore Tso
2009-08-16 0:44 ` David Wagner
2009-08-16 1:33 ` Theodore Tso
2009-08-16 8:18 ` david
2009-08-17 0:31 ` David Wagner
2009-08-17 2:22 ` Theodore Tso
2009-08-17 2:45 ` James Morris
2009-08-17 3:16 ` Arjan van de Ven [this message]
2009-08-21 14:02 ` Pavel Machek
2009-08-22 17:22 ` Henrique de Moraes Holschuh
2009-08-17 1:39 ` Amerigo Wang
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=20090816201606.6e96efc8@infradead.org \
--to=arjan@infradead.org \
--cc=daw-news@cs.berkeley.edu \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tytso@mit.edu \
/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