Bug 985758 - SELinux is preventing /usr/bin/updatedb from read, write access on the file /var/lib/mlocate/mlocate.db.
Summary: SELinux is preventing /usr/bin/updatedb from read, write access on the file /...
Keywords:
Status: CLOSED DUPLICATE of bug 985757
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9f6c89ac70c6acfd3b0400d8768...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-18 07:56 UTC by Jan Sedlák
Modified: 2013-07-18 13:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-18 13:47:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jan Sedlák 2013-07-18 07:56:55 UTC
Description of problem:
SELinux is preventing /usr/bin/updatedb from read, write access on the file /var/lib/mlocate/mlocate.db.

*****  Plugin restorecon (94.8 confidence) suggests  *************************

If you want to fix the label. 
/var/lib/mlocate/mlocate.db default label should be locate_var_lib_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /var/lib/mlocate/mlocate.db

*****  Plugin catchall_labels (5.21 confidence) suggests  ********************

If you want to allow updatedb to have read write access on the mlocate.db file
Then you need to change the label on /var/lib/mlocate/mlocate.db
Do
# semanage fcontext -a -t FILE_TYPE '/var/lib/mlocate/mlocate.db'
where FILE_TYPE is one of the following: afs_cache_t, initrc_tmp_t, locate_var_lib_t, puppet_tmp_t, user_cron_spool_t, user_tmp_t. 
Then execute: 
restorecon -v '/var/lib/mlocate/mlocate.db'


*****  Plugin catchall (1.44 confidence) suggests  ***************************

If you believe that updatedb should be allowed read write access on the mlocate.db 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 updatedb /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:locate_t:s0-s0:c0.c1023
Target Context                system_u:object_r:unlabeled_t:s0
Target Objects                /var/lib/mlocate/mlocate.db [ file ]
Source                        updatedb
Source Path                   /usr/bin/updatedb
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           mlocate-0.26-3.fc19.x86_64
Target RPM Packages           mlocate-0.26-3.fc19.x86_64
Policy RPM                    selinux-policy-3.12.1-63.fc19.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.9.9-302.fc19.x86_64 #1 SMP Sat
                              Jul 6 13:41:07 UTC 2013 x86_64 x86_64
Alert Count                   3
First Seen                    2013-07-16 11:45:11 CEST
Last Seen                     2013-07-18 03:40:17 CEST
Local ID                      5ce44a16-7875-45bb-9829-4a9bdf5022e1

Raw Audit Messages
type=AVC msg=audit(1374111617.224:658): avc:  denied  { read write } for  pid=17176 comm="updatedb" name="mlocate.db" dev="dm-2" ino=2366488 scontext=system_u:system_r:locate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file


type=SYSCALL msg=audit(1374111617.224:658): arch=x86_64 syscall=open success=no exit=EACCES a0=7f327e701c99 a1=2 a2=0 a3=7f327f0dc850 items=0 ppid=17170 pid=17176 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=18 tty=(none) comm=updatedb exe=/usr/bin/updatedb subj=system_u:system_r:locate_t:s0-s0:c0.c1023 key=(null)

Hash: updatedb,locate_t,unlabeled_t,file,read,write

Additional info:
reporter:       libreport-2.1.5
hashmarkername: setroubleshoot
kernel:         3.9.9-302.fc19.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2013-07-18 13:47:47 UTC

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


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