From: Diyab <diyab@diyab.net>
To: Michael Reilly <michaelr@cisco.com>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: setfiles and /home labeling
Date: Wed, 15 Oct 2003 22:12:51 -0400 [thread overview]
Message-ID: <3F8DFEA3.5000701@diyab.net> (raw)
In-Reply-To: <20031015160109.7fbdbb12.michaelr@cisco.com>
Michael Reilly wrote:
> I know I am missing something. These are all of the lines from
> file_contexts which reference the /home directories. Notice the two lines
> which reference /home/michaelr. After running make relabel /home/michaelr
> is labeled system_u:object_r:user_home_dir_t instead of
> system_u:object_r:staff_home_dir_t and all of the files in /home/michaelr
> and below (except the files special cased like .ssh, etc.) are labeled
> system_u:object_r:user_home_t.
>
> Why are the two lines for /home/michaelr being ignored? What am I doing
> wrong?
>
> Thanks,
>
> michael
> # Ordinary user home directories.
> /home system_u:object_r:home_root_t
> /home/[^/]+ -d system_u:object_r:user_home_dir_t
> /home/[^/]+/.+ system_u:object_r:user_home_t
> # Other staff home directories, replace "jadmin" with appropriate name
> /home/michaelr/(/.*)? system_u:object_r:staff_home_t
> /home/michaelr system_u:object_r:staff_home_dir_t
You have an extra / in the staff_home_t declaration. Change it to read
like this:
/home/michaelr(/.*)? system_u:object_r:staff_home_t
Timothy,
--
I put instant coffee in a microwave and almost went back in time.
-- Steven Wright
--
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 prev parent reply other threads:[~2003-10-16 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 23:01 setfiles and /home labeling Michael Reilly
2003-10-16 1:30 ` Russell Coker
2003-10-16 1:45 ` Michael Reilly
2003-10-16 2:12 ` Diyab [this message]
2003-10-16 5:35 ` Michael Reilly
2003-10-16 12:32 ` 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=3F8DFEA3.5000701@diyab.net \
--to=diyab@diyab.net \
--cc=michaelr@cisco.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.