[CentOS] Bind data directory borked on update from 5.3 to 5.4
Brian Mathis
brian.mathis at gmail.comThu Jan 21 14:38:12 UTC 2010
- Previous message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Next message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 21, 2010 at 8:20 AM, Kai Schaetzl <maillists at conactive.com> wrote: > Kai Schaetzl wrote on Thu, 21 Jan 2010 13:00:48 +0100: > >> I wonder now if the owner of >> that directory should actually be named? > > Hm, after looking on other machines that have named installed but not in > use it's excactly the same there. So, if named wants write permission > there, but the rpm always removes that permission - isn't the rpm wrong > then? Should I report this as a bug? > > Kai I don't think you'd want a compromised named to be able to make changes to your authoritative DNS records, which is what could happen if you have permissions set that way.
- Previous message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Next message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list