Bug 243512 - SELinux is preventing /usr/sbin/useradd (useradd_t) "read write" to faillog (var_log_t).
Summary: SELinux is preventing /usr/sbin/useradd (useradd_t) "read write" to faillog (...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: shadow-utils
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-09 10:14 UTC by Martin Jürgens
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-11 11:16:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
selinux alert (2.29 KB, text/plain)
2007-06-09 10:14 UTC, Martin Jürgens
no flags Details

Description Martin Jürgens 2007-06-09 10:14:13 UTC
Description of problem:
When installing BackupPC with yum, SELinux blocks something:

SELinux is preventing /usr/sbin/useradd (useradd_t) "read write" to faillog
    (var_log_t).

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


How reproducible:


Steps to Reproduce:
1. Install BackupPC
2.
3.
  
Actual results:
SELinux warning

Expected results:
Nothing

Additional info:

Comment 1 Martin Jürgens 2007-06-09 10:14:14 UTC
Created attachment 156640 [details]
selinux alert

Comment 2 Peter Vrabec 2007-06-11 08:43:15 UTC
I can't reproduce it, but my context on /var/log/faillog is 
-rw-------  root root system_u:object_r:faillog_t      /var/log/faillog

Martin, could you run:
#restorecon /var/log/faillog
and see if context changed.

Comment 3 Martin Jürgens 2007-06-11 11:16:12 UTC
Just uninstalled it and installed it again, no error message.

Don't ask me what was wrong. I am going to reopen this bug if it reappears.

Comment 4 Daniel Walsh 2007-06-11 14:33:32 UTC
There is a knoqn problem on initial installs and upgrades of the faillog file
getting the wrong context.  This should be fixed on upgrades going forward. 
restorecon -R -v /var/log should fix the problem.


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