Description of problem: SELinux is preventing pool-geoclue from 'search' accesses on the directory net. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that pool-geoclue should be allowed search access on the net directory 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 'pool-geoclue' --raw | audit2allow -M my-poolgeoclue # semodule -X 300 -i my-poolgeoclue.pp Additional Information: Source Context system_u:system_r:geoclue_t:s0 Target Context system_u:object_r:sysctl_net_t:s0 Target Objects net [ dir ] Source pool-geoclue Source Path pool-geoclue Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.8-2.fc38.noarch Local Policy RPM selinux-policy-targeted-38.8-2.fc38.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.2.11-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 13 20:27:09 UTC 2023 x86_64 Alert Count 44 First Seen 2023-04-15 07:54:06 BST Last Seen 2023-04-15 08:49:02 BST Local ID 7b9befff-e905-4da5-bb1f-9175b01f82fa Raw Audit Messages type=AVC msg=audit(1681544942.703:329): avc: denied { search } for pid=3198 comm="pool-geoclue" name="net" dev="proc" ino=37329 scontext=system_u:system_r:geoclue_t:s0 tcontext=system_u:object_r:sysctl_net_t:s0 tclass=dir permissive=0 Hash: pool-geoclue,geoclue_t,sysctl_net_t,dir,search Version-Release number of selected component: selinux-policy-targeted-38.8-2.fc38.noarch Additional info: reporter: libreport-2.17.9 kernel: 6.2.11-300.fc38.x86_64 reason: SELinux is preventing pool-geoclue from 'search' accesses on the directory net. package: selinux-policy-targeted-38.8-2.fc38.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport component: selinux-policy
Created attachment 1957566 [details] File: os_info
Created attachment 1957567 [details] File: description
*** This bug has been marked as a duplicate of bug 2183190 ***