This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2230508 - SELinux File context are not showing correct information as expected - authselect backup files with etc_t but dir expects var_lib_t
Summary: SELinux File context are not showing correct information as expected - authse...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.8
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 15:14 UTC by Prashant Thakur
Modified: 2023-09-13 08:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-13 08:14:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fedora-selinux selinux-policy pull 1869 0 None open Set default file context of /var/lib/authselect/backups to <<none>> 2023-09-11 08:18:09 UTC
Red Hat Issue Tracker   RHEL-3539 0 None Migrated None 2023-09-13 08:14:01 UTC
Red Hat Issue Tracker RHELPLAN-165136 0 None None None 2023-08-09 15:15:51 UTC

Comment 2 Zdenek Pytela 2023-08-23 08:36:00 UTC 
I can't currently see anything which could be done in selinux-policy, it seems the files are copied with preserving all attributes, i. e. including SELinux context.
Switching the component to assess if it is reasonable to make any change in the process.
Comment 3 Pavel Březina 2023-08-25 10:53:15 UTC 
(In reply to Zdenek Pytela from comment #2)
> I can't currently see anything which could be done in selinux-policy, it
> seems the files are copied with preserving all attributes, i. e. including
> SELinux context.
> Switching the component to assess if it is reasonable to make any change in
> the process.

Yes, you are correct. Authselect creates backup by copying files and preserving all attributes so they can be correctly restored later. From my perspective, this is correct behavior, but I will follow suggestions from selinux team.
Comment 5 Pavel Březina 2023-09-01 12:40:53 UTC 
Setting need info for Zdenek per https://bugzilla.redhat.com/show_bug.cgi?id=2230508#c3
Comment 6 Zdenek Pytela 2023-09-08 19:12:45 UTC 
(In reply to Pavel Březina from comment #3)
> (In reply to Zdenek Pytela from comment #2)
> > I can't currently see anything which could be done in selinux-policy, it
> > seems the files are copied with preserving all attributes, i. e. including
> > SELinux context.
> > Switching the component to assess if it is reasonable to make any change in
> > the process.
> 
> Yes, you are correct. Authselect creates backup by copying files and
> preserving all attributes so they can be correctly restored later. From my
> perspective, this is correct behavior, but I will follow suggestions from
> selinux team.

If the directory is preset, we can possibly set default ruleset in policy to <<none>> which means no check is performed. If it varies or is a subject of configuration, I can't see any reasonable solution and the bug can be closed. In the former case feel free to switch it back to selinux-policy.
Comment 7 Pavel Březina 2023-09-11 07:31:35 UTC 
The directory is preset, not configurable. Switching back to selinux-policy.
Comment 8 RHEL Program Management 2023-09-13 08:12:09 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9 RHEL Program Management 2023-09-13 08:14:07 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.