public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: daw@cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: Security: information leaks in /proc enable keystroke recovery
Date: Sun, 16 Aug 2009 00:44:14 +0000 (UTC)	[thread overview]
Message-ID: <h67kou$ahr$1@taverner.cs.berkeley.edu> (raw)
In-Reply-To: 20090816003326.GC7554@mit.edu

Theodore Tso  wrote:
> A configuration option which defaults to disabling ESP and EIP would
> be a simple way to prevent this specific instance of information
> leakage.  The problem is there are other files that might reveal
> timing information, but which are very useful for a system
> administrator.  A key example of this is /proc/$pid/wchan, which is
> responsible for the WCHAN column is a ps listing.

If they're useful for system administrators, would making them
readable to root (but not everyone) be enough?

  reply	other threads:[~2009-08-16  0:53 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 [this message]
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
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='h67kou$ahr$1@taverner.cs.berkeley.edu' \
    --to=daw@cs.berkeley.edu \
    --cc=daw-news@cs.berkeley.edu \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox