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.

Created attachment 1961104 [details]
journalctl centos stream 9

Description of problem:
Selinux blocks wg-quick from establishing a wireguard connection.
This is probably the same bug I also have on Fedora 38:
https://bugzilla.redhat.com/show_bug.cgi?id=2192140

After running "sudo setenforce 0" the connection can be established.

The wireguard config was created by ProtonVPN.

I will add the journalctl output from Centos Stream 9 and the redacted wireguard config as an attachment.


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


How reproducible:
Always

Steps to Reproduce:
1. Get a wireguard config from ProtonVPN
2. (I commented out the "DNS" option in the config file)
3. Copy it to /etc/wireguard
4. Try to establish a connection by running "systemctl start wg-quick@config_name"

Actual results:
The wireguard connection cannot be established

Expected results:
The wireguard connection can be established

Additional info:

Created attachment 1961105 [details]
redacted wireguard config

Hi Stephan, 

Please reproduce the issue in permissive mode:

# setenforce 0

And collect AVC denials:
# ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today

Thank you

Hi,

did that, on a newly installed, fully updated CentOS Stream 9 machine. selinux-policy is now at version 38.1.12.
I will upload the output as an attachment.

Created attachment 1961807 [details]
collected AVC denials

The attached SELinux denials indicate that the following rules are missing in SELinux policy:

allow wireguard_t sysctl_net_t : dir { search };
allow wireguard_t sysctl_net_t : file { getattr open write };
allow iptables_t wireguard_t : fifo_file { open };

The attached file also contains 1 SELinux denial related to plymouthd which is already reported as:
 * https://bugzilla.redhat.com/show_bug.cgi?id=2184803

So, I tested it on CentOS Stream 9 now and it works. Looks to me like the bug is fixed. Nice work, thank you 👍

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 (selinux-policy 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:6617