Red Hat Bugzilla – Bug 994578
File permission change took down my servers
Last modified: 2013-08-26 08:23:32 EDT
Description of problem:
Upgrade changed file permissions causing PDNS to fail
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I know you will probably say it's my fault for not having all the file owners be pdns but when the upgrade ran and changed the file permissions to 700 it took down all my DNS servers. Before you modify permissions on other people's servers you might want to check if you are going to break it. You might want to consider that there may be a reason other people don't set things up the same way you do.
Going from working to not working is not an upgrade.
Which file permissions exactly?
There is only one change to fix https://bugzilla.redhat.com/show_bug.cgi?id=646510
Steps to reproduce this? (I'm not able to reproduce this)
The owner of pdns.conf was root. When you changed the access to 600 then the pdns process running under the user pdns couldn't read the pdns.conf file. I probably should have had pdns be the owner of pdns.conf but I didn't. It used to have 755 permissions and that worked.
I think that making the assumption that you can just change permissions because it makes things more secure runs the risk that you can break things.
(In reply to Marc Perkel from comment #2)
> The owner of pdns.conf was root. When you changed the access to 600 then the
> pdns process running under the user pdns couldn't read the pdns.conf file.
The owner of pdns.conf is still root and there is no issue to read the pdns.conf file with 600 file permissions.
I suspect that this is a local problem with your installation.
This is a local problem and not a bug = closed.