From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: How to handle lots of executables buried in /usr
Date: Mon, 24 Nov 2003 10:01:57 -0500 [thread overview]
Message-ID: <3FC21D65.5070803@redhat.com> (raw)
I am seeing lots of errors in policy because of shell scripts and exes
that are installed in subdirectories of /usr being marked as usr_t
instead of bin_t . What do you guys think of adding a script to be
executed after make relabel that would find these files and change their
context to bin_t.
find /usr -perm +111 --context system_u:object_r:usr_t -type f -exec
chcon \
system_u:object_r:bin_t {} ; -print
Is this a bad idea? I do notice that their are a lot of files marked
executables by their install that are really not executable, but this
would clean up several failures untill the package installs are cleaned up.
Dan
--
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:[~2003-11-24 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 15:01 Daniel J Walsh [this message]
2003-11-24 19:00 ` How to handle lots of executables buried in /usr Stephen Smalley
2003-11-24 22:44 ` 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=3FC21D65.5070803@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.