Bug 833230 - sssd unable to create pipes and read files with selinux enforcing
Summary: sssd unable to create pipes and read files with selinux enforcing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: selinux-policy
Version: 5.8
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-19 00:15 UTC by lance dillon
Modified: 2012-06-19 13:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-19 13:23:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description lance dillon 2012-06-19 00:15:45 UTC
Description of problem:
sssd unable to create pipes under /var/lib/sss/pipes, or read krb5 cache file in /tmp

Version-Release number of selected component (if applicable):
1.5.1-49.1

How reproducible:
install ipa-client, or service sssd start/restart

Comment 1 lance dillon 2012-06-19 00:18:14 UTC
The following policy file solved the problem for me:

policy_module(sq_sssd, 1.3)

require {
    type sssd_t;
    type sssd_var_lib_t;
    type tmp_t;
    class lnk_file { read write create };
    class file { getattr read };
}

#============= sssd_t ==============
allow sssd_t sssd_var_lib_t:lnk_file { create read write };
allow sssd_t tmp_t:file { getattr read };


This of course could probably be shortened with macros.

Comment 2 Milos Malik 2012-06-19 06:39:51 UTC
Which version of selinux-policy packages is installed on your machine?

Comment 3 lance dillon 2012-06-19 11:49:58 UTC
selinux-policy-2.4.6-327.el5

Comment 4 lance dillon 2012-06-19 11:54:32 UTC
Just had an additional entry in audit.log, audit2allow reported this:

#============= sssd_t ==============
allow sssd_t tmp_t:file { read lock getattr unlink };

Comment 5 Stephen Gallagher 2012-06-19 12:33:47 UTC
Please include the original AVCs that you were seeing as well.

Comment 6 lance dillon 2012-06-19 13:21:06 UTC
Upon further investigation and discussion on #sssd, it appears that selinux-policy may have been updated after sssd was started, so the policy wasn't applied yet.  I'm not encountering the problem currently, can't seem to reproduce (I've tried on a couple of different systems), so I'm going to close this, if I can.


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