Re: ps aux output under sysadm context in refpolicy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2008-02-21 at 15:22 -0600, Jeremiah Jahn wrote:
> I'm having a heck of a time limiting the ps aux output to show only what
> I think sysadm should be able to see.
> 
> I have a number of types that are running and I get a ptrace denied, but
> sysadm can still see the process. I'm really not sure why this is the
> case. I've set all the build options correctly, ie left the defaults,
> the booleans are set to no. Somewhere there is something going on that
> lets sysadm see all of this stuff, and I just can't find it.
> 
> According to apol there is not way for me to read the proc files as
> sysadm. What Am I missing, or where should I look.

Access to the basic /proc/pid information is allowed by:
	# search the /proc/pid directory for the target domain
	allow <source domain> <target domain>:dir search;
	# read public information about the target domain
	allow <source domain> <target domain>:file read;
since the /proc/pid files are labeled with the domain of the associated
process.

Certain /proc/pid nodes are further limited by ptrace since they reveal
what should be private information to the process.

> 
> thanx,
> -jj-
> 
> 
> 
> He thought he saw an albatross That fluttered 'round the lamp. He looked
> again and saw it was A penny postage stamp. "You'd best be getting
> home," he said, "The nights are rather damp."
-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux