Bug 2214080

Summary: SELinux is preventing key.dns_resolve from 'execute' accesses on the file /usr/sbin/key.dns_resolver.
Product: [Fedora] Fedora Reporter: Davide Repetto <red>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: dwalsh, lvrabec, mmalik, nknazeko, omosnacek, pkoncity, red, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2a372e541b88170e744e0c08a060431151966260c7edea15b51c7045c23bea6c;VARIANT_ID=matecompiz;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-12 10:32:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Davide Repetto 2023-06-11 16:53:29 UTC
Description of problem:
SELinux is preventing key.dns_resolve from 'execute' accesses on the file /usr/sbin/key.dns_resolver.

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

Se ci credi key.dns_resolve dovrebbe essere consentito execute accesso al key.dns_resolver file per impostazione predefinita.
Then si dovrebbe riportare il problema come bug.
E' possibile generare un modulo di politica locale per consentire questo accesso.
Do
consentire questo accesso per ora eseguendo:
# ausearch -c 'key.dns_resolve' --raw | audit2allow -M my-$MODULE_NOME
# semodule -X 300 -i miei-keydnsresolve.pp

Additional Information:
Source Context                system_u:system_r:keyutils_dns_resolver_t:s0
Target Context                system_u:object_r:keyutils_dns_resolver_exec_t:s0
Target Objects                /usr/sbin/key.dns_resolver [ file ]
Source                        key.dns_resolve
Source Path                   key.dns_resolve
Port                          <Sconosciuto>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           keyutils-1.6.1-6.fc38.x86_64
SELinux Policy RPM            selinux-policy-targeted-38.15-1.fc38.noarch
Local Policy RPM              selinux-policy-targeted-38.15-1.fc38.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 6.3.6-200.fc38.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Mon Jun 5 15:45:04 UTC 2023 x86_64
Alert Count                   1
First Seen                    2023-06-11 18:48:55 CEST
Last Seen                     2023-06-11 18:48:55 CEST
Local ID                      3520725a-a61b-446e-996e-23d5376256b6

Raw Audit Messages
type=AVC msg=audit(1686502135.328:244): avc:  denied  { execute } for  pid=3276 comm="key.dns_resolve" path="/usr/sbin/key.dns_resolver" dev="sde4" ino=12367621 scontext=system_u:system_r:keyutils_dns_resolver_t:s0 tcontext=system_u:object_r:keyutils_dns_resolver_exec_t:s0 tclass=file permissive=1


Hash: key.dns_resolve,keyutils_dns_resolver_t,keyutils_dns_resolver_exec_t,file,execute

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

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

Comment 1 Davide Repetto 2023-06-11 16:53:31 UTC
Created attachment 1970316 [details]
File: description

Comment 2 Davide Repetto 2023-06-11 16:53:33 UTC
Created attachment 1970317 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-06-12 10:32:18 UTC

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