All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: We are seeing more and more programs accessing sysfs_t.
Date: Tue, 13 Dec 2011 15:44:15 -0500	[thread overview]
Message-ID: <1323809055.21623.39.camel@moss-pluto> (raw)
In-Reply-To: <4EE7B79A.7000101@redhat.com>

On Tue, 2011-12-13 at 15:37 -0500, Daniel J Walsh wrote:
> -----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.

Modern kernels support setfilecon()/setxattr() on sysfs nodes, so a
userspace program can set specific types on them.  That was added a
couple of years ago for libvirt.  Just specify the desired labels in
file_contexts and restorecon -R /sys at boot.

-- 
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@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2011-12-13 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 20:37 We are seeing more and more programs accessing sysfs_t Daniel J Walsh
2011-12-13 20:44 ` Stephen Smalley [this message]

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=1323809055.21623.39.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=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.