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 1759212 - ptp4l not allowed to use L2 transport
Summary: ptp4l not allowed to use L2 transport
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-07 15:46 UTC by Miroslav Lichvar
Modified: 2023-09-14 05:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1759214 (view as bug list)
Environment:
Last Closed: 2020-08-05 05:56:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Miroslav Lichvar 2019-10-07 15:46:01 UTC 
Description of problem:
When ptp4l is configured to use the L2 transport, it fails to open the raw socket due to a selinux policy. In the permissive mode I get the following AVCs:

type=AVC msg=audit(1570462720.524:1061): avc:  denied  { create } for  pid=10793 comm="ptp4l" scontext=system_u:system_r:ptp4l_t:s0 tcontext=system_u:system_r:ptp4l_t:s0 tclass=packet_socket permissive=1
type=AVC msg=audit(1570462720.524:1062): avc:  denied  { ioctl } for  pid=10793 comm="ptp4l" path="socket:[38157]" dev="sockfs" ino=38157 ioctlcmd=8933 scontext=system_u:system_r:ptp4l_t:s0 tcontext=system_u:system_r:ptp4l_t:s0 tclass=packet_socket permissive=1
type=AVC msg=audit(1570462720.524:1063): avc:  denied  { bind } for  pid=10793 comm="ptp4l" scontext=system_u:system_r:ptp4l_t:s0 tcontext=system_u:system_r:ptp4l_t:s0 tclass=packet_socket permissive=1
type=AVC msg=audit(1570462720.530:1064): avc:  denied  { setopt } for  pid=10793 comm="ptp4l" scontext=system_u:system_r:ptp4l_t:s0 tcontext=system_u:system_r:ptp4l_t:s0 tclass=packet_socket permissive=1


Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-259.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. change OPTIONS in /etc/sysconfig/ptp4l to "-i eth0 --network_transport L2"
2. systemctl restart ptp4l
3. check audit log

Actual results:
AVC errors reported in audit log and ptp4l complains in system log
ptp4l[10816]: [2771.015] socket failed: Permission denied
ptp4l[10816]: [2771.015] port 1: INITIALIZING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)

Expected results:
No errors reported

Additional info:
Comment 2 Zdenek Pytela 2019-10-08 07:06:02 UTC 
This issue was not selected to be included in Red Hat Enterprise Linux 7 because it is seen either as low or moderate impact to a small number of use-cases. The next minor release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open and describe the impact of this issue.
Comment 7 Red Hat Bugzilla 2023-09-14 05:44:12 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.