Bug 2292481 - SELinux is preventing systemd-fstab-g from 'create' accesses on the file .#50-device-timeout.conf9e05e243d3d01690.
Summary: SELinux is preventing systemd-fstab-g from 'create' accesses on the file .#50...
Keywords:
Status: CLOSED DUPLICATE of bug 2292191
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 40
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:862b7a4c888eec7091ca6b66df3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-15 07:15 UTC by Philipp Raich
Modified: 2024-06-17 16:01 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-06-17 16:01:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (2.19 KB, text/plain)
2024-06-15 07:15 UTC, Philipp Raich
no flags Details
File: os_info (734 bytes, text/plain)
2024-06-15 07:15 UTC, Philipp Raich
no flags Details

Description Philipp Raich 2024-06-15 07:15:17 UTC
Description of problem:
SELinux is preventing systemd-fstab-g from 'create' accesses on the file .#50-device-timeout.conf9e05e243d3d01690.

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

If you believe that systemd-fstab-g should be allowed create access on the .#50-device-timeout.conf9e05e243d3d01690 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 'systemd-fstab-g' --raw | audit2allow -M my-systemdfstabg
# semodule -X 300 -i my-systemdfstabg.pp

Additional Information:
Source Context                system_u:system_r:systemd_fstab_generator_t:s0
Target Context                system_u:object_r:systemd_cryptsetup_generator_uni
                              t_file_t:s0
Target Objects                .#50-device-timeout.conf9e05e243d3d01690 [ file ]
Source                        systemd-fstab-g
Source Path                   systemd-fstab-g
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.22-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.22-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.8.11-300.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Mon May 27 14:53:33 UTC 2024
                              x86_64
Alert Count                   2
First Seen                    2024-06-15 08:39:17 CEST
Last Seen                     2024-06-15 08:39:17 CEST
Local ID                      50cea0f7-dbb7-4d49-8f11-43fb711fbc73

Raw Audit Messages
type=AVC msg=audit(1718433557.596:521): avc:  denied  { create } for  pid=11385 comm="systemd-fstab-g" name=".#50-device-timeout.conf9e05e243d3d01690" scontext=system_u:system_r:systemd_fstab_generator_t:s0 tcontext=system_u:object_r:systemd_cryptsetup_generator_unit_file_t:s0 tclass=file permissive=0


Hash: systemd-fstab-g,systemd_fstab_generator_t,systemd_cryptsetup_generator_unit_file_t,file,create

Version-Release number of selected component:
selinux-policy-targeted-40.22-1.fc40.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing systemd-fstab-g from 'create' accesses on the file .#50-device-timeout.conf9e05e243d3d01690.
package:        selinux-policy-targeted-40.22-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.8.11-300.fc40.x86_64
component:      selinux-policy

Comment 1 Philipp Raich 2024-06-15 07:15:19 UTC
Created attachment 2037408 [details]
File: description

Comment 2 Philipp Raich 2024-06-15 07:15:21 UTC
Created attachment 2037409 [details]
File: os_info

Comment 3 Zdenek Pytela 2024-06-17 16:01:26 UTC

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


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