Red Hat Bugzilla – Bug 877418
/etc/dhcp not world readable
Last modified: 2015-02-17 09:34:17 EST
Description of problem:
The /etc/dhcp directory has permissions set to 0750, which makes it inconvenient for the users to check the content, namely the dhclient.d scripts. Usually, directories in /etc have 0755 permissions, unless there is a good reason to hide them.
It seems the change was done to fix the bug #508247, but in the original Gentoo they eventually closed it as WONTFIX.
Please consider reverting back to 0755 permissions.
Is there a reason why a user would need to look at the dhclient.d scripts? If they were interested in changing them, they'd need to be root anyways, right?
I don't think those scripts are necessarily sensitive, so the permissions on /etc/dhcp could possibly be relaxed (ensuring that dhcpd.conf retains 700 or 750 permissions), but I also don't really see a need for the relaxed permissions either (on the basis that if the user wanted to change any of those scripts, they'd need to be root).
This is one of the regressions I was talking about in bug #508247.
I'm also not sure I buy the "inconvenient to users" argument as this change was made almost 3.5 years ago and this is the first objection we've seen regarding it.
Perhaps I should have written that it's inconvenient to me :). I'm a maintainer of some packages that put files in the the dhclient.d directory and I regret I didn't file this bug sooner.
Why should not be dhcpd.conf world-readable? From the discussion in the original Gentoo bug referenced in the bug #508247 it seems there is no sensitive data in the file. FWIW, the Debian package has the file readable too.
I think it's a matter of handing out minimal information. The average user wouldn't need this info. Taking a look at the file, there doesn't seem to be (at least not in my config) a lot of sensitive info. rndc key isn't in there (but it could be, I suppose, depending on the admin), and the rest could _possibly_ be found out by network scanners assuming that any static-assigned ip machines noted were also on the network at the time of the scan.
It's an information disclosure issue that isn't super sensitive that I can see, but I do think the principle of least information is a good principle to follow as there are then no surprises. =)
Having said that, I wouldn't necessarily be opposed to keeping dhcpd.conf locked down but opening up /etc/dhcp to 711 or something so that a user could get to /etc/dhcp/dhclient.d/ files to peek at them.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.