Description of problem: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that nm-openconnect- should be allowed setsched access on processes labeled vpnc_t by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'nm-openconnect-' --raw | audit2allow -M my-nmopenconnect # semodule -X 300 -i my-nmopenconnect.pp Additional Information: Source Context system_u:system_r:vpnc_t:s0 Target Context system_u:system_r:vpnc_t:s0 Target Objects Unknown [ process ] Source nm-openconnect- Source Path nm-openconnect- Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-3.14.5-28.fc32.noarch Local Policy RPM selinux-policy-targeted-3.14.5-28.fc32.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.6.0-0.rc4.git0.1.fc32.x86_64 #1 SMP Mon Mar 2 22:32:50 UTC 2020 x86_64 x86_64 Alert Count 1 First Seen 2020-03-10 20:44:26 GMT Last Seen 2020-03-10 20:44:26 GMT Local ID 182bb116-235a-4097-8e2b-7a593e6c7a1e Raw Audit Messages type=AVC msg=audit(1583873066.743:507): avc: denied { setsched } for pid=45964 comm="nm-openconnect-" scontext=system_u:system_r:vpnc_t:s0 tcontext=system_u:system_r:vpnc_t:s0 tclass=process permissive=0 Hash: nm-openconnect-,vpnc_t,vpnc_t,process,setsched Version-Release number of selected component: selinux-policy-3.14.5-28.fc32.noarch Additional info: component: selinux-policy reporter: libreport-2.12.0 hashmarkername: setroubleshoot kernel: 5.6.0-0.rc4.git0.1.fc32.x86_64 type: libreport Potential duplicate: bug 1806442
Similar problem has been detected: Connected to VPN using NetworkManager hashmarkername: setroubleshoot kernel: 5.6.2-300.fc32.x86_64 package: selinux-policy-3.14.5-32.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: I have upgradet to Fedora 32. Login as usual. Then Startet VPN with Cisco Anyconnect Protokoll. Login + VPN works. SELinux pops up. hashmarkername: setroubleshoot kernel: 5.6.7-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-32.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: Simple vpn connection hashmarkername: setroubleshoot kernel: 5.6.7-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-32.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
*** Bug 1829962 has been marked as a duplicate of this bug. ***
Also have this bug. This is new with fedora 32.
Similar problem has been detected: I think it must have been opening a VPN connection. hashmarkername: setroubleshoot kernel: 5.6.8-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-32.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: Toggling an openconnect VPN on using the GNOME panel option. hashmarkername: setroubleshoot kernel: 5.6.8-300.fc32.x86_64 reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: Must have happened when I started an OpenConnect VPN connection. Not sure why this time. hashmarkername: setroubleshoot kernel: 5.6.8-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-38.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: connected to VPN hashmarkername: setroubleshoot kernel: 5.6.10-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-38.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: Established openconnect VPN connection hashmarkername: setroubleshoot kernel: 5.6.10-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-38.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
Similar problem has been detected: After using NetworkManager to establish the connection to my VPN. It's the first I did it after the Fedora 32 upgrade. It sounds like NetworkManager tries to elevate privilege for open-connect so it can be realtime, but it's not allowed by selinux. hashmarkername: setroubleshoot kernel: 5.6.13-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-38.fc32.noarch reason: SELinux is preventing nm-openconnect- from using the 'setsched' accesses on a process. type: libreport
*** Bug 1840764 has been marked as a duplicate of this bug. ***
*** Bug 1846595 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1817528 ***