Red Hat Bugzilla – Bug 597318
A freshly installed Fedora 13 box with NIS authentication selected doesn't set allow_ypbind in SELinux
Last modified: 2011-06-02 09:37:24 EDT
Description of problem:
I installed Fedora 13 from the release disc, and chose NIS authentication in the
Unfortunately, it seems that choosing NIS authentication in the firstboot configurator is not enough to tell Fedora 13 to turn on the 'allow_ypbind' SELinux boolean.
Version-Release number of selected component (if applicable):
Fedora 13, ypbind-1.31.2.fc13, selinux-policy-22.214.171.124.fc13
Install Fedora 13, select NIS user authentication. Wait for things to explode.
Steps to Reproduce:
1. Install Fedora 13
2. Select NIS user authentication
3. Try and fail to login, notice allow_ypbind is not enabled.
Breakage. Seemingly random NIS failures at login time.. though sometimes login does succeed despite allow_ypbind not being enabled.
Have allow_ypbind enabled in the SELinux boolean set when NIS authentication is chosen at install time.
Reassigning to firstboot, as ypbind itself cannot set allow_ypbind SELinux boolean.
Maybe it should be reassigned to authconfig-gtk (system-config-authentication), I am not sure who should set allow_ypbind.
Assigning back, sorry, it's mine. The allow_ypbind is set in the ypbind init script.
can you please uncomment the following lines in /etc/init.d/ypbind.init, functions selinux_on and selinux_off:
#echo $"Turning on allow_ypbind SELinux boolean"
#echo $"Turning off allow_ypbind SELinux boolean"
and check if "Turning on allow_ypbind..." appears when ypbind is started during boot.
With packages ypbind-1.31-3.fc13 (installed by yum update) I see that allow_ypbind is set on after reboot with ypbind configured to start on boot.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
(In reply to comment #4)
> With packages ypbind-1.31-3.fc13 (installed by yum update) I see that
> allow_ypbind is set on after reboot with ypbind configured to start on boot.
I think this bug can be closed.
Closing because of comment #7 and it works for me too.