John Levon <[EMAIL PROTECTED]> wrote: > Please explain the privacy issue. Are you trying to suggest that the > profile of an application might reveal something private to a user? Note > there is no way to correlate such a profile back to an individual user.
It can reveal, e.g., which library and system calls does an user's program make. > Given that the alternative involves running all the userspace report > tools as root or under sudo, I find it very difficult to believe that > this option is somehow more secure. Not really, as you can add the user to the adm group. As a non-administrator has currently no way to use oprofile, this shouldn't be a problem. Adm group membership is already needed to read system logs. > People who are worried about this should: > [...] > 2) chmod the directories themselves This should, at the very least, be documented. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
