From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Currently the kernel is interpreting reading the link file on /proc/PID/exe as sys_ptrace for a different UID.
Date: Mon, 13 Feb 2012 16:49:54 -0500 [thread overview]
Message-ID: <4F398582.7030004@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I believe this should be DAC_READ_SEARCH.
I am trying to prevent all SYS_PTRACE from any domain on the system
but certain apps like dbus, consolekit, policykit, systemd-logger and
others like to look /proc/PID/exe to report the path of the executable
they are communicating with. This causes lots of sys_ptrace access
being required for domains, that I do not believe need it.
They need DAC_READ_SEARCH because they are trying to read content that
is owned by a different UID. The SYS_PTRACE stuff was put in to
prevent apps from reading process memory information stored in /proc.
I think this is a bug in the kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk85hYIACgkQrlYvE4MpobPnsACcDXrEipv+rkdDa1/E4TwQdrtj
z9IAn2yCwDDdAvUIxiSugzMJQZUzswJ1
=Tfwm
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2012-02-13 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 21:49 Daniel J Walsh [this message]
2012-02-13 23:09 ` Currently the kernel is interpreting reading the link file on /proc/PID/exe as sys_ptrace for a different UID Stephen Smalley
2012-02-14 13:57 ` Daniel J Walsh
2012-02-21 20:36 ` Stephen Smalley
2012-02-21 21:54 ` Daniel J Walsh
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=4F398582.7030004@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.