From: Daniel J Walsh <dwalsh@redhat.com>
To: Colin Walters <walters@verbum.org>
Cc: Yuichi Nakamura <himainu-ynakam@miomio.jp>,
sds@epoch.ncsc.mil, selinux@tycho.nsa.gov
Subject: Re: idea: setfiles to exclude specific type
Date: Mon, 22 Nov 2004 14:27:55 -0500 [thread overview]
Message-ID: <41A23DBB.5010704@redhat.com> (raw)
In-Reply-To: <1101151201.28164.28.camel@nexus.verbum.private>
Colin Walters wrote:
>On Mon, 2004-11-22 at 10:54 -0500, Yuichi Nakamura wrote:
>
>
>>Hello.
>>
>>I add setfiles "-x" option.
>>I attach my idea in "setfiles.diff".
>>
>>-x option is used to exclude specified type.
>>
>>For example,
>># setfiles file_contexts /home -x httpd_user_rw_t
>>setfiles skips relabeling files that have "httpd_user_rw_t".
>>
>>
>
>I thought the conclusion from previous discussion on user-customizable
>file contexts was that we were going to add notation to file_contexts
>for groups of contexts, so that all of e.g.
>system_u:object_r:httpd_sys_content_t,
>system_u:object_r:httpd_sys_script_exec_t,
>system_u:object_r:httpd_sys_script_rw_t,
>etc. would be acceptable.
>
>For example:
>
>/var/www(/.*)? system_u:object_r:httpd_sys_content_t system_u:object_r:httpd_sys_script_rw_t system_u:object_r:httpd_sys_script_exec_t ...
>
>
>
>
I am not sure that works, and I kind of like the idea of adding a
attribute to a context to maintain it.
Certain contexts we want to make the admin force a change on, usually
these are contexts that the user used chcon to create, or mv to make a
copy of it. So if a user creates a /var/web account with
httpd_sys_content_rw_t, we would hammer it, but if we put
httpd_content_t in a don't change category fixfiles will leave it alone
by default. The other main example would be, the user makes a copy of
his gpg_keys and restorecon/setfiles/fixfiles changes them to
user_home_t which is readable by other domains.
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.
prev parent reply other threads:[~2004-11-22 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:54 idea: setfiles to exclude specific type Yuichi Nakamura
2004-11-22 17:00 ` Daniel J Walsh
2004-11-22 17:58 ` Yuichi Nakamura
2004-11-22 19:20 ` Colin Walters
2004-11-22 19:27 ` Daniel J Walsh [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=41A23DBB.5010704@redhat.com \
--to=dwalsh@redhat.com \
--cc=himainu-ynakam@miomio.jp \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.org \
/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.