From: Petr Lautrbach <plautrba@redhat.com>
To: Ted Toth <txtoth@gmail.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: file context not being set on el7
Date: Fri, 21 Sep 2018 10:58:27 +0200 [thread overview]
Message-ID: <pjdfty3447g.fsf@redhat.com> (raw)
In-Reply-To: <CAFPpqQG3_aUEJW8fbz8sRtTPRcw2KUsQ+wtr3+-awjcws+PD0w@mail.gmail.com>
Ted Toth <txtoth@gmail.com> writes:
> I have something very much like the following in an fc file:
> /usr/lib64/python2\.(6|7)/site-packages/xyz/paste --
> gen_context(system_u:object_r:jxyz_exec_t,s0)
>
> and I use the same file on el6 and el7. On el6 the file is
> labeled as
> specified in the python2.6 directory. However on el7 where the
> file gets
> installed into python2.7 the file is not labeled correctly. On
> el7
> `semanage fcontext -l | grep xyz` shows the file context
> expected but
> `matchpathcon /usr/lib64/python2.7/site-packages/xyz/paste` does
> not return
> the expected context and `restorecon -RFv
> /usr/lib64/python2.7/site-packages/xyz` has no affect. The type
> xyz_exec_t
> exists on both systems. It's probably something stupid I'm doing
> but I'm
> just not seeing it. Has anyone else experienced similar issues?
>
There's equivalency rule /usr/lib64 -> /usr/lib on el7:
# semanage fcontext -a -t tmp_t
'/usr/lib64/python2\.(6|7)/site-packages/xyz/paste'
ValueError: File spec
/usr/lib64/python2\.(6|7)/site-packages/xyz/paste conflicts with
equivalency rule '/usr/lib64 /usr/lib'; Try adding
'/usr/lib/python2\.(6|7)/site-packages/xyz/paste' instead
# semanage fcontext -a -t tmp_t
'/usr/lib/python2\.(6|7)/site-packages/xyz/paste'
# matchpathcon /usr/lib64/python2.7/site-packages/xyz/paste
/usr/lib64/python2.7/site-packages/xyz/paste
system_u:object_r:tmp_t:s0
Petr
next prev parent reply other threads:[~2018-09-21 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 21:35 file context not being set on el7 Ted Toth
2018-09-21 8:58 ` Petr Lautrbach [this message]
2018-09-21 12:21 ` Ted Toth
2018-09-21 13:19 ` Ted Toth
2018-09-24 18:54 ` Petr Lautrbach
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=pjdfty3447g.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.com \
/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.