Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
wg-quick@.service fails if endpoint contains dns name
Version-Release number of selected component (if applicable):
1.0.20210914
How reproducible:
Attempt to start the wg-quick@.service using a configuration file containing a peer with an Endpoint = <dns-name>:port with SELinux enforcing and with SELinux permissive.
wg-quick@.service fails with "Name or service not known: '<dns-name>:51820'"
Initial selinux issues worked around with the following policy but no further audit log denial entries appear.
require {
type net_conf_t;
type wireguard_t;
class udp_socket { connect create getattr setopt };
class file { getattr open read };
}
#============= wireguard_t ==============
#!!!! This avc is allowed in the current policy
allow wireguard_t net_conf_t:file { getattr open read };
#!!!! This avc is allowed in the current policy
allow wireguard_t self:udp_socket { connect create setopt };
allow wireguard_t self:udp_socket getattr;
Steps to Reproduce:
1. Create wg-quick configuration file, wg0.conf, with Peer section containing `Endpoint = <dns-name>:port`
2. systemctl start wg-quick
Actual results:
Service fails to start. Logs show error "Name or service not known"
Expected results:
Service starts successfully.
Additional info:
'setenforce 0' allows the service to start successfully. Additionally, manual calls of wg-quick up <conf-file> work with and without selinux in enforcing mode. Failure is only observed in systemd service.
Description of problem: wg-quick@.service fails if endpoint contains dns name Version-Release number of selected component (if applicable): 1.0.20210914 How reproducible: Attempt to start the wg-quick@.service using a configuration file containing a peer with an Endpoint = <dns-name>:port with SELinux enforcing and with SELinux permissive. wg-quick@.service fails with "Name or service not known: '<dns-name>:51820'" Initial selinux issues worked around with the following policy but no further audit log denial entries appear. require { type net_conf_t; type wireguard_t; class udp_socket { connect create getattr setopt }; class file { getattr open read }; } #============= wireguard_t ============== #!!!! This avc is allowed in the current policy allow wireguard_t net_conf_t:file { getattr open read }; #!!!! This avc is allowed in the current policy allow wireguard_t self:udp_socket { connect create setopt }; allow wireguard_t self:udp_socket getattr; Steps to Reproduce: 1. Create wg-quick configuration file, wg0.conf, with Peer section containing `Endpoint = <dns-name>:port` 2. systemctl start wg-quick Actual results: Service fails to start. Logs show error "Name or service not known" Expected results: Service starts successfully. Additional info: 'setenforce 0' allows the service to start successfully. Additionally, manual calls of wg-quick up <conf-file> work with and without selinux in enforcing mode. Failure is only observed in systemd service.