Bug 848693 - /usr/libexec/sesh is not labelled correctly
/usr/libexec/sesh is not labelled correctly
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: selinux-policy (Show other bugs)
All Linux
medium Severity medium
: beta
: ---
Assigned To: Miroslav Grepl
Milos Malik
Depends On:
  Show dependency treegraph
Reported: 2012-08-16 04:40 EDT by Milos Malik
Modified: 2013-01-07 22:33 EST (History)
3 users (show)

See Also:
Fixed In Version: selinux-policy-2.4.6-332.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-01-07 22:33:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milos Malik 2012-08-16 04:40:12 EDT
Description of problem:
SELinux policy believes that sesh is installed in /usr/sbin directory, but it is installed in /usr/libexec directory. Therefore the existing file is labelled incorrectly.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
# matchpathcon /usr/sbin/sesh
/usr/sbin/sesh  system_u:object_r:shell_exec_t
# matchpathcon /usr/libexec/sesh
/usr/libexec/sesh       system_u:object_r:bin_t
# rpm -ql sudo | grep sesh
# ls -Z /usr/sbin/sesh
ls: /usr/sbin/sesh: No such file or directory

Actual results:
 * incorrect label

Expected results:
 * correct label
Comment 1 RHEL Product and Program Management 2012-08-16 04:57:13 EDT
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 3 Miroslav Grepl 2012-09-04 10:42:47 EDT
Fixed in selinux-policy-2.4.6-332.el5
Comment 8 errata-xmlrpc 2013-01-07 22:33:04 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.