Bug 428156 - SELinux is preventing /usr/sbin/logrotate (logrotate_t) "write" to (NetworkManager_log_t).
Summary: SELinux is preventing /usr/sbin/logrotate (logrotate_t) "write" to (NetworkMa...
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-09 17:50 UTC by Dave Allan
Modified: 2008-10-20 15:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-10-20 15:06:03 UTC
Type: ---

Attachments (Terms of Use)

Description Dave Allan 2008-01-09 17:50:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20071213 Fedora/ Firefox/

Description of problem:
Source Context:  system_u:system_r:logrotate_t:s0Target Context:  unconfined_u:object_r:NetworkManager_log_t:s0Target Objects:  None [ file ]Affected RPM Packages:  logrotate-3.7.6-1.3.fc8 [application]Policy RPM:  selinux-policy-3.0.8-72.fc8Selinux Enabled:  TruePolicy Type:  targetedMLS Enabled:  TrueEnforcing Mode:  EnforcingPlugin Name:  plugins.catchall_fileHost Name:  merryPlatform:  Linux merry #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686Alert Count:  2First Seen:  Tue 08 Jan 2008 10:25:06 PM ESTLast Seen:  Wed 09 Jan 2008 12:25:59 PM ESTLocal ID:  237d95c1-9859-4af3-8422-defc07d0ce22Line Numbers:  Raw Audit Messages :avc: denied { write } for comm=logrotate dev=sda2 egid=0 euid=0 exe=/usr/sbin/logrotate exit=-13 fsgid=0 fsuid=0 gid=0 items=0 name=wpa_supplicant.log pid=3525 scontext=system_u:system_r:logrotate_t:s0 sgid=0 subj=system_u:system_r:logrotate_t:s0 suid=0 tclass=file tcontext=unconfined_u:object_r:NetworkManager_log_t:s0 tty=(none) uid=0 

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

How reproducible:
Didn't try

Steps to Reproduce:

Actual Results:

Expected Results:

Additional info:

Comment 1 Dan Williams 2008-10-20 14:44:16 UTC
do you still get this with recent policy updates and recent NetworkManager?  Pretty sure this is gone now...

Comment 2 Dave Allan 2008-10-20 15:06:03 UTC
Yep--I haven't seen it in months.  I've closed it as 'worksforme' which is a bit odd, as I opened it, but I figure that's the closest option, since I don't know how or when it was fixed.

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