Bug 1033843 (selinux_shm_backingstore_f20) - SELinux is preventing /usr/sbin/smbd from read, write access on the file /SYSV07021999 (deleted).
Summary: SELinux is preventing /usr/sbin/smbd from read, write access on the file /SYS...
Keywords:
Status: CLOSED EOL
Alias: selinux_shm_backingstore_f20
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e13dad5804bf5efa7c599c3844a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-23 17:33 UTC by hx
Modified: 2023-09-14 01:54 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:45:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description hx 2013-11-23 17:33:34 UTC
Description of problem:
tried to set up samba
SELinux is preventing /usr/sbin/smbd from read, write access on the file /SYSV07021999 (deleted).

*****  Plugin restorecon (63.0 confidence) suggests   ************************

If you want to fix the label. 
/SYSV07021999 (deleted) default label should be etc_runtime_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /SYSV07021999 (deleted)

*****  Plugin samba_share (32.3 confidence) suggests   ***********************

If you want to allow smbd to have read write access on the SYSV07021999 (deleted) file
Then you need to change the label on '/SYSV07021999.(deleted)'
Do
# semanage fcontext -a -t samba_share_t '/SYSV07021999.(deleted)'
# restorecon  -v '/SYSV07021999.(deleted)'

*****  Plugin catchall_boolean (5.5 confidence) suggests   *******************

If you want to allow samba to export all rw
Then you must tell SELinux about this by enabling the 'samba_export_all_rw' boolean.
You can read 'None' man page for more details.
Do
setsebool -P samba_export_all_rw 1

*****  Plugin catchall (1.12 confidence) suggests   **************************

If you believe that smbd should be allowed read write access on the SYSV07021999 (deleted) 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:
# grep smbd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:smbd_t:s0
Target Context                system_u:object_r:tmpfs_t:s0
Target Objects                /SYSV07021999 (deleted) [ file ]
Source                        smbd
Source Path                   /usr/sbin/smbd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           samba-4.1.1-1.fc20.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-90.fc20.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 3.11.8-300.fc20.x86_64 #1 SMP Wed
                              Nov 13 16:34:27 UTC 2013 x86_64 x86_64
Alert Count                   4
First Seen                    2013-11-23 18:42:00 EET
Last Seen                     2013-11-23 19:32:05 EET
Local ID                      b6f63cd2-bb06-49d9-81d2-36297915cdcf

Raw Audit Messages
type=AVC msg=audit(1385227925.30:571): avc:  denied  { read write } for  pid=2586 comm="smbd" path=2F535953563037303231393939202864656C6574656429 dev="tmpfs" ino=0 scontext=system_u:system_r:smbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file


type=SYSCALL msg=audit(1385227925.30:571): arch=x86_64 syscall=shmat success=yes exit=140348486328320 a0=0 a1=0 a2=0 a3=7fa56a9147b8 items=0 ppid=1 pid=2586 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=smbd exe=/usr/sbin/smbd subj=system_u:system_r:smbd_t:s0 key=(null)

Hash: smbd,smbd_t,tmpfs_t,file,read,write

Additional info:
reporter:       libreport-2.1.9
hashmarkername: setroubleshoot
kernel:         3.11.8-300.fc20.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2013-11-25 14:00:15 UTC
Are you able to get it again?

Comment 2 Daniel Walsh 2013-11-25 14:53:25 UTC
We have a duplicate of this bug, which I think is a kernel issue.

Comment 3 Paul Moore 2014-01-27 22:52:00 UTC
See my comments in BZ #1013878, there is nothing we can do to resolve this in the kernel.  Reassigning to policy.

Comment 4 Miroslav Grepl 2014-01-28 10:27:07 UTC
*** Bug 1013878 has been marked as a duplicate of this bug. ***

Comment 5 Miroslav Grepl 2014-01-28 10:28:37 UTC
I tried to add a type transition.

Comment 6 Fedora End Of Life 2015-05-29 09:50:08 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-06-30 00:45:00 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Red Hat Bugzilla 2023-09-14 01:54:19 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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