Bug 2208106 - SELinux is preventing request-key from 'execute' accesses on the file /usr/sbin/key.dns_resolver.
Summary: SELinux is preventing request-key from 'execute' accesses on the file /usr/sb...
Keywords:
Status: CLOSED DUPLICATE of bug 2182643
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:885b4102348658cdf1f7da1be0a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-18 01:51 UTC by Nick Fenwick
Modified: 2023-05-18 08:19 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-18 08:19:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (1.99 KB, text/plain)
2023-05-18 01:51 UTC, Nick Fenwick
no flags Details
File: os_info (734 bytes, text/plain)
2023-05-18 01:51 UTC, Nick Fenwick
no flags Details

Description Nick Fenwick 2023-05-18 01:51:05 UTC
Description of problem:
Since upgrading to Fedora 38 Workstation (from 37) I've had this regular popup.  It doesn't seem to be interfering with system functions, it's just really annoying.

SELinux is preventing request-key from 'execute' accesses on the file /usr/sbin/key.dns_resolver.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that request-key should be allowed execute access on the key.dns_resolver file 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 'request-key' --raw | audit2allow -M my-requestkey
# semodule -X 300 -i my-requestkey.pp

Additional Information:
Source Context                system_u:system_r:keyutils_request_t:s0
Target Context                system_u:object_r:bin_t:s0
Target Objects                /usr/sbin/key.dns_resolver [ file ]
Source                        request-key
Source Path                   request-key
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           keyutils-1.6.1-6.fc38.x86_64
SELinux Policy RPM            selinux-policy-targeted-38.12-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.12-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.2.15-300.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu May 11 17:37:39 UTC 2023
                              x86_64
Alert Count                   869
First Seen                    2023-05-01 11:16:28 +07
Last Seen                     2023-05-18 08:20:50 +07
Local ID                      7a875423-6365-4c75-a9d1-780031221362

Raw Audit Messages
type=AVC msg=audit(1684372850.683:836): avc:  denied  { execute } for  pid=39996 comm="request-key" name="key.dns_resolver" dev="nvme0n1p6" ino=12982061 scontext=system_u:system_r:keyutils_request_t:s0 tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0


Hash: request-key,keyutils_request_t,bin_t,file,execute

Version-Release number of selected component:
selinux-policy-targeted-38.12-1.fc38.noarch

Additional info:
reporter:       libreport-2.17.10
reason:         SELinux is preventing request-key from 'execute' accesses on the file /usr/sbin/key.dns_resolver.
package:        selinux-policy-targeted-38.12-1.fc38.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.2.15-300.fc38.x86_64
component:      selinux-policy

Comment 1 Nick Fenwick 2023-05-18 01:51:08 UTC
Created attachment 1965330 [details]
File: description

Comment 2 Nick Fenwick 2023-05-18 01:51:11 UTC
Created attachment 1965331 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-05-18 08:19:37 UTC

*** This bug has been marked as a duplicate of bug 2182643 ***


Note You need to log in before you can comment on or make changes to this bug.