From: Lee Revell <rlrevell@joe-job.com>
To: David Wagner <daw-usenet@taverner.CS.Berkeley.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] getrusage sucks
Date: Fri, 11 Nov 2005 14:09:58 -0500 [thread overview]
Message-ID: <1131736199.5758.27.camel@mindpipe> (raw)
In-Reply-To: <dl18ro$l0f$1@taverner.CS.Berkeley.EDU>
On Fri, 2005-11-11 at 05:06 +0000, David Wagner wrote:
> Claudio Scordino wrote:
> >Does exist any _real_ reason why getrusage can't be invoked by a task to know
> >statistics of another task ?
>
> Probably only super-user should be permitted to read the usage information
> about other processes. Allowing anyone to read anyone else's rusage would
> open up a bunch of side channels that sound pretty dangerous. For instance,
> user #1 might be able to mount a timing attack against crypto code being
> executed by user #2, and that doesn't sound good.
Why restrict it to root? Why not just prevent users from reading other
users rusage. How could it be a security hole for joeuser's process be
able to read the rusage of joeuser's other processes?
Lee
next prev parent reply other threads:[~2005-11-11 19:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 22:34 [PATCH] getrusage sucks Claudio Scordino
2005-11-11 5:06 ` David Wagner
2005-11-11 19:09 ` Lee Revell [this message]
2005-11-11 19:13 ` David Wagner
2005-11-12 17:45 ` How to quickly detect the mode change of a hard disk? Hui Cheng
2005-11-13 15:10 ` Pavel Machek
2005-11-16 18:58 ` Alejandro Bonilla
2005-11-18 19:41 ` Hui Cheng
2005-11-19 23:44 ` Pavel Machek
2005-11-22 15:39 ` Hui Cheng
-- strict thread matches above, loose matches on Subject: below --
2005-11-10 23:47 [PATCH] getrusage sucks Hua Zhong (hzhong)
2005-11-11 0:23 ` Claudio Scordino
2005-11-11 0:32 ` Magnus Naeslund(f)
2005-11-11 1:11 ` Claudio Scordino
2005-11-11 13:30 ` Alan Cox
2005-11-11 22:38 ` Claudio Scordino
2005-11-11 23:23 ` Alan Cox
2005-11-11 23:02 ` Chris Wright
2005-11-11 23:44 ` David Wagner
2005-11-12 0:53 ` Chris Wright
2005-11-12 6:37 ` David Wagner
2005-11-11 23:58 ` Alan Cox
2005-11-11 23:43 ` Claudio Scordino
2005-11-11 23:49 ` dean gaudet
2005-11-12 1:10 ` Chris Wright
2005-11-13 1:34 ` Claudio Scordino
2005-11-15 16:56 ` Claudio Scordino
2005-11-11 23:08 ` Claudio Scordino
2005-11-11 23:41 ` David Wagner
2005-11-15 1:08 ` Peter Chubb
2005-11-11 23:49 Hua Zhong (hzhong)
2005-11-15 18:25 linux
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=1131736199.5758.27.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=daw-usenet@taverner.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