To: linux-kernel@vger.kernel.org
Path: not-for-mail
From: daw@cs.berkeley.edu (David Wagner)
Newsgroups: isaac.lists.linux-kernel
Subject: Re: [PATCH] getrusage sucks
Date: Fri, 11 Nov 2005 23:44:39 +0000 (UTC)
Organization: University of California, Berkeley
Message-ID: <dl3ad7$ikf$2@taverner.CS.Berkeley.EDU>
References: <75D9B5F4E50C8B4BB27622BD06C2B82BCF2FD4@xmb-sjc-235.amer.cisco.com> <200511112338.20684.cloud.of.andor@gmail.com> <1131751433.3174.50.camel@localhost.localdomain> <20051111230223.GB7991@shell0.pdx.osdl.net>
Reply-To: daw-usenet@taverner.CS.Berkeley.EDU (David Wagner)
NNTP-Posting-Host: taverner.cs.berkeley.edu
NNTP-Posting-Date: Fri, 11 Nov 2005 23:44:39 +0000 (UTC)
Originator: daw@taverner.cs.berkeley.edu (David Wagner)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 629
Lines: 8

Chris Wright  wrote:
>It's already available via /proc w/out protection.  And ditto via posix
>cpu timers.

If so, maybe that code should be fixed.  Where exactly in /proc would
I find the getrusage() info of another process?  Is there any argument
that disclosing it to everyone is safe?  Or is it just that no one has
ever given the security considerations much thought up till now?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/