Bug 155843 - not enabling named_write_master_zones
not enabling named_write_master_zones
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
:
Depends On:
Blocks: FC4Target
  Show dependency treegraph
 
Reported: 2005-04-24 11:57 EDT by Gene Czarcinski
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-28 14:14:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2005-04-24 11:57:54 EDT
Description of problem:

In order to support dynamic dns updating by dhcpd, you need to enable (set to 1)
the variable named_write_master_zones in /etc/selinux/targeted/booleans

the named startup script uses this variable (if set to 1) to change ownership of
/var/named/chroot/var/named so that named can write to that directory.

Although you can check and uncheck the box in system-config-securitylevel it has
no effect on changing the variable in /etc/selinux/targeted/booleans
Comment 1 Daniel Walsh 2005-04-28 11:12:05 EDT
Gene it should be changing this in /etc/selinux/targeted/booleans.local?
Comment 2 Daniel Walsh 2005-04-28 11:14:08 EDT
I just tried it here and it worked.

more booleans.local
allow_ypbind=0
named_write_master_zones=1

getsebool named_write_master_zones
named_write_master_zones --> active
Comment 3 Gene Czarcinski 2005-04-28 12:09:12 EDT
OK, boolean.local is a change (at least to me) because earlier versions (e.g.,
FC3) changed the value in /etc/selinux/targeted/booleans

Now, named_write_master_zones is defined in both /etc/selinux/targeted/booleans
and /etc/selinux/targeted/booleans.local but which takes precidence?  If it is
set to "1" in booleans will setting it to "0" in booleans.local be ignored?  How
about  the reverse?
Comment 4 Gene Czarcinski 2005-04-28 12:11:42 EDT
One additional point ... setting named_write_master_zones to 1 in booleans is
not recognized by systems-config-securitylevel ... only settings in booleans.local.
Comment 5 Chris Lumens 2005-04-28 13:18:15 EDT
Yes, booleans.local takes precedence over whatever's defined in booleans.  Think
of it as the difference between global environment settings and per-user
environment settings.
Comment 6 Gene Czarcinski 2005-04-28 14:14:41 EDT
Ok, I am satisfied that there is no bug and am closing this.

I was not aware of the booleans.local ... it might be a good idea to add
something about this to RELEASE-NOTES

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