Bug 2041054 - SELinux is preventing lightdm-gtk-gre from 'write' accesses on the sock_file bus.
Summary: SELinux is preventing lightdm-gtk-gre from 'write' accesses on the sock_file ...
Keywords:
Status: CLOSED DUPLICATE of bug 2039671
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ffc400a775a54af4b37ae98a581...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-15 16:07 UTC by Woi
Modified: 2022-02-02 16:29 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-02 16:29:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Woi 2022-01-15 16:07:53 UTC
Description of problem:
SELinux is preventing lightdm-gtk-gre from 'write' accesses on the sock_file bus.

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

Wenn Sie denken, dass es lightdm-gtk-gre standardmäßig erlaubt sein sollte, write Zugriff auf bus sock_file zu erhalten.
Then sie sollten dies als Fehler melden.
Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen.
Do
zugriff jetzt erlauben, indem Sie die nachfolgenden Befehle ausführen:
# ausearch -c 'lightdm-gtk-gre' --raw | audit2allow -M my-lightdmgtkgre
# semodule -X 300 -i my-lightdmgtkgre.pp

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                unconfined_u:object_r:session_dbusd_tmp_t:s0
Target Objects                bus [ sock_file ]
Source                        lightdm-gtk-gre
Source Path                   lightdm-gtk-gre
Port                          <Unbekannt>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-34.23-1.fc34.noarch
Local Policy RPM              selinux-policy-targeted-34.23-1.fc34.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 5.15.13-100.fc34.x86_64 #1 SMP Wed
                              Jan 5 17:06:02 UTC 2022 x86_64 x86_64
Alert Count                   32
First Seen                    2022-01-12 10:00:29 CET
Last Seen                     2022-01-15 17:06:38 CET
Local ID                      1aa5cf23-3c41-4f05-8787-024e66f85850

Raw Audit Messages
type=AVC msg=audit(1642262798.927:373): avc:  denied  { write } for  pid=19779 comm="pool-lightdm-gt" name="bus" dev="tmpfs" ino=47 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:session_dbusd_tmp_t:s0 tclass=sock_file permissive=0


Hash: lightdm-gtk-gre,xdm_t,session_dbusd_tmp_t,sock_file,write

Version-Release number of selected component:
selinux-policy-targeted-34.23-1.fc34.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.15.2
hashmarkername: setroubleshoot
kernel:         5.15.13-100.fc34.x86_64
type:           libreport

Comment 1 baramavraham 2022-01-18 05:11:23 UTC
Similar problem has been detected:

After system restart and login SELinux notified me of this issue.

hashmarkername: setroubleshoot
kernel:         5.15.14-100.fc34.x86_64
package:        selinux-policy-targeted-34.23-1.fc34.noarch
reason:         SELinux is preventing lightdm-gtk-gre from 'write' accesses on the sock_file bus.
type:           libreport

Comment 2 Wilhelm.Buchmueller 2022-02-02 16:19:47 UTC
Similar problem has been detected:

selinux write error on each run of lightdm-gtk-greeter.

hashmarkername: setroubleshoot
kernel:         5.15.16-100.fc34.x86_64
package:        selinux-policy-targeted-34.23-1.fc34.noarch
reason:         SELinux is preventing lightdm-gtk-gre from 'write' accesses on the sock_file bus.
type:           libreport

Comment 3 Zdenek Pytela 2022-02-02 16:29:56 UTC

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


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