Bug 991848

Summary:	SELinux is preventing /usr/bin/chage from using the 'transition' accesses on a process.
Product:	[Fedora] Fedora	Reporter:	Suawomirr <slawomir.iwanek>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	dominick.grift, dwalsh, mgrepl
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:774ebcadecd8e6c262815f31fb9aba97bc0e248168286f3e1c42f53659af266f
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 22:14:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Suawomirr 2013-08-05 00:40:02 UTC

Description of problem:
I created a new account on the system with just plain 'useradd NAME' (no password setting commands) and right after that I issued 'chage -d 0 NAME' for that account to check if I could set a new password at first login attempt. The output was:
chage: cannot execute /usr/sbin/nscd: Brak dostępu
chage: nscd exited with status 126
chage: Failed to flush the nscd cache.
chage: cannot execute /usr/sbin/nscd: Brak dostępu
chage: nscd exited with status 126
chage: Failed to flush the nscd cache.

After issueing passwd -d NAME and passwd -e NAME everything all right.

Again issued chage -d 0 NAME. Same output as above but logging into NAME have let me to change the password.

Additional info about nscd at my machine:

systemctl status nscd
nscd.service - Name Service Cache Daemon
Loaded: loaded (/usr/lib/systemd/system/nscd.service; disabled)
Active: inactive (dead)

And:

rpm -qf /bin/chage
shadow-utils-4.1.5.1-2.fc18.x86_64

LANG=C nscd --version
nscd (GNU libc) 2.16
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Thorsten Kukuk and Ulrich Drepper.

Additional info:
reporter: libreport-2.1.5
hashmarkername: setroubleshoot
kernel: 3.9.11-200.fc18.x86_64
type: libreport

Potential duplicate: bug 948631

Comment 1 Fedora End Of Life 2013-12-21 14:26:04 UTC

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 22:14:03 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.