From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: We are seeing more and more programs accessing sysfs_t.
Date: Tue, 13 Dec 2011 15:37:46 -0500 [thread overview]
Message-ID: <4EE7B79A.7000101@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Every domain is now reading /sys/devices/system/cpu/online because of
changes to glibc.
We are also seeing domains that need write access.
For example
> https://bugzilla.redhat.com/show_bug.cgi?id=685096
>
> for https://bugzilla.redhat.com/show_bug.cgi?id=685096 (IP over
> Infiniband support for NetworkManager), NM needs to be able to
> write to /sys/class/net/ib*/mode. audit2allow says:
>
> allow NetworkManager_t sysfs_t:file write;
It seems we need a better way of labeling files under /sys.
genfscon only seems to work at the top level.
Allowing all domains to read sysfs_t does not seem like the correct
solution, and allow NetworkManager to write anywhere on /sys is
probably not good either.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7nt5oACgkQrlYvE4MpobOyfwCfav6hMLyB5kPcAJvW81zhqC7o
s30AoJv2aI8RmLi8gDq2gGMjadiyLziP
=PVUp
-----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:[~2011-12-13 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 20:37 Daniel J Walsh [this message]
2011-12-13 20:44 ` We are seeing more and more programs accessing sysfs_t Stephen Smalley
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=4EE7B79A.7000101@redhat.com \
--to=dwalsh@redhat.com \
--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.