Bug 680689 - SELinux is preventing /usr/kerberos/sbin/krb5kdc from 'unlink' accesses on the file krb5kdc_rcache.
Summary: SELinux is preventing /usr/kerberos/sbin/krb5kdc from 'unlink' accesses on th...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 13
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:05524ced5d7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 00:41 UTC by James Harrion
Modified: 2011-03-11 15:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 15:26:52 UTC
Type: ---


Attachments (Terms of Use)

Description James Harrion 2011-02-27 00:41:24 UTC
SELinux is preventing /usr/kerberos/sbin/krb5kdc from 'unlink' accesses on the file krb5kdc_rcache.

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

If you believe that krb5kdc should be allowed unlink access on the krb5kdc_rcache 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 krb5kdc /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:system_r:krb5kdc_t:s0
Target Context                system_u:object_r:tmp_t:s0
Target Objects                krb5kdc_rcache [ file ]
Source                        krb5kdc
Source Path                   /usr/kerberos/sbin/krb5kdc
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           krb5-server-1.7.1-17.fc13
Target RPM Packages           
Policy RPM                    selinux-policy-3.7.19-80.fc13
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.34.7-66.fc13.i686.PAE #1
                              SMP Wed Dec 15 07:21:49 UTC 2010 i686 i686
Alert Count                   2
First Seen                    Sat 26 Feb 2011 07:35:57 PM EST
Last Seen                     Sat 26 Feb 2011 07:36:19 PM EST
Local ID                      a54ad8db-f51e-4972-8419-eeb65e82b3d8

Raw Audit Messages
type=AVC msg=audit(1298766979.181:1003): avc:  denied  { unlink } for  pid=9488 comm="krb5kdc" name="krb5kdc_rcache" dev=dm-1 ino=270680 scontext=unconfined_u:system_r:krb5kdc_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=file


type=SYSCALL msg=audit(1298766979.181:1003): arch=i386 syscall=unlink success=no exit=EACCES a0=16d7ab0 a1=0 a2=dd8884 a3=16d7e0c items=0 ppid=9487 pid=9488 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=14 comm=krb5kdc exe=/usr/kerberos/sbin/krb5kdc subj=unconfined_u:system_r:krb5kdc_t:s0 key=(null)

Hash: krb5kdc,krb5kdc_t,tmp_t,file,unlink

audit2allow

#============= krb5kdc_t ==============
allow krb5kdc_t tmp_t:file unlink;

audit2allow -R

#============= krb5kdc_t ==============
allow krb5kdc_t tmp_t:file unlink;

Comment 1 James Harrion 2011-02-27 00:47:23 UTC
Hi all,
I thought I should submit this as a bug. Maybe its nothing. Just doing my bit.

Comment 2 Miroslav Grepl 2011-02-28 09:49:43 UTC
If you change the label for krb5kdc_rcache

# chcon -t krb5kdc_tmp_t PATHTO/krb5kdc_rcache


Can you reproduce it then?

Comment 3 James Harrion 2011-02-28 10:23:43 UTC
I have since run the commands:
# grep krb5kdc /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

and it no longer happens, but I could always reproduce it using:
service krb5kdc start

The init script wouldn't start the service.

Comment 4 Miroslav Grepl 2011-02-28 13:12:15 UTC
(In reply to comment #3)
> I have since run the commands:
> # grep krb5kdc /var/log/audit/audit.log | audit2allow -M mypol
> # semodule -i mypol.pp

Yes, it does not happen with the local policy.

> 
> and it no longer happens, but I could always reproduce it using:
> service krb5kdc start
> 
> The init script wouldn't start the service.

So did you run krb5kdc directly? I mean without using a service script.


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