All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Why is customizing labeling and seusers so SLOOOOOOOWWWWW.
Date: Fri, 08 Aug 2008 11:37:54 -0400	[thread overview]
Message-ID: <489C6852.7060501@redhat.com> (raw)

Is it time to move seuser and local file context labeling out of
libsemanage?  I have just heard from the virt team that they want to
modify the context of a virt machine at creation time, so they have
looked at chcon -t virt_image_t.  They understand that changing the
image will not survive a relabel but

"Unfortunately, semanage is rather slow application to run. It also
pulls in the entire python runtime, which isn't something we can do in
libvirt. We really need some light-weight way of adding new file
contexts to the policy persistently."

I explained they can call libsemanage via "C"  but the comment brings up
a point of why does semanage recompile policy when changing file context
or the seusers file.  All we really need to do is verify the contests
are correct and this should be a very fast operation.

--
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:[~2008-08-08 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 15:37 Daniel J Walsh [this message]
2008-08-08 16:51 ` Why is customizing labeling and seusers so SLOOOOOOOWWWWW Joshua Brindle
2008-08-08 20:51   ` 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=489C6852.7060501@redhat.com \
    --to=dwalsh@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.