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 2136738 - Listening socket has incorrect label when SELinuxContextFromNet=yes is set
Summary: Listening socket has incorrect label when SELinuxContextFromNet=yes is set
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.5
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On: 2135794
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-21 06:20 UTC by Michal Sekletar
Modified: 2023-05-16 11:11 UTC (History)
5 users (show)

Fixed In Version: systemd-239-70.el8
Doc Type: Enhancement
Doc Text:
Clone Of: 2135794
Environment:
Last Closed: 2023-05-16 09:07:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 345 0 None open Use target process context to set socket context 2022-12-08 12:02:30 UTC
Github systemd systemd pull 24994 0 None Merged Use target process context to set socket context 2022-10-24 11:31:04 UTC
Red Hat Issue Tracker RHELPLAN-137246 0 None None None 2022-10-21 06:25:53 UTC
Red Hat Product Errata RHBA-2023:2985 0 None None None 2023-05-16 09:08:18 UTC

Description Michal Sekletar 2022-10-21 06:20:43 UTC
+++ This bug was initially created as a clone of Bug #2135794 +++

Description of problem:
When we start to listen on socket that has SELinuxContextFromNet=yes we compute SELinux label of the socket using systemd's own label instead of label of target executable that is launched by the triggered service.

Version-Release number of selected component (if applicable):
systemd-250-12.el9_1.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
Patch for test case Sanity/SELinuxContextFromNet which exhibits the issue is attached.

Actual results:
Patched test case fails.


Expected results:
Patched test case passes.


Additional info:
https://github.com/systemd/systemd/pull/24994

--- Additional comment from David Tardon on 2022-10-19 09:22:03 CEST ---



--- Additional comment from Ted X Toth on 2022-10-19 14:57:41 CEST ---

Can this be backported to RHEL 8?

Comment 1 Plumber Bot 2023-01-12 12:10:39 UTC
fix merged to github main branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/345

Comment 7 errata-xmlrpc 2023-05-16 09:07:33 UTC
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 (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2023:2985


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