RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1697894 - MLS: /var/lib/rsyslog/imjournal.state context is not appropriate
Summary: MLS: /var/lib/rsyslog/imjournal.state context is not appropriate
Keywords:
Status: CLOSED DUPLICATE of bug 1673107
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 8.1
Assignee: Lukas Vrabec
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1673107
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-09 09:08 UTC by Renaud Métrich
Modified: 2019-06-11 08:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-11 08:20:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Renaud Métrich 2019-04-09 09:08:11 UTC 
Description of problem:

When running in MLS mode, rsyslog's /var/lib/rsyslog/imjournal.state context is created with system_u:object_r:syslogd_var_lib_t:s15:c0.c1023 because rsyslogd runs as system_u:system_r:syslogd_t:s15:c0.c1023.
However, the policy states the file should have context system_u:object_r:syslogd_var_lib_t:s0


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

selinux-policy-mls-3.14.1-61.el8.noarch


How reproducible:

Always


Steps to Reproduce:
1. Boot in MLS mode
2. Check the context

# ls -Z /var/lib/rsyslog/imjournal.state; echo; matchpathcon /var/lib/rsyslog/imjournal.state


Actual results:

system_u:object_r:syslogd_var_lib_t:s15:c0.c1023 /var/lib/rsyslog/imjournal.state

/var/lib/rsyslog/imjournal.state	system_u:object_r:syslogd_var_lib_t:s0
Comment 2 Lukas Vrabec 2019-06-11 08:20:28 UTC 

*** This bug has been marked as a duplicate of bug 1673107 ***
Note You need to log in before you can comment on or make changes to this bug.