topic Re: /etc/resolv.conf in Operating System - HP-UX

/etc/resolv.conf

joe_91 — Wed, 17 Jul 2002 16:29:01 GMT

Hi There:

We currently have the resolv.conf file permission as 666. Ok. we are going to change it to 644.My questions..
1. is 644 OK?
2. what are the side effects of 666 (other than some one can play around with the file), I mean will it have resolving issues etc..

Thanks in advance,

Joe.

Re: /etc/resolv.conf

James R. Ferguson — Wed, 17 Jul 2002 16:30:53 GMT

Hi Joe:

Yes, 666 is far too dangerous. Permissions of 644 or even 444 (since you can still edit it as 'root') are far more appropriate and safe.

Regards!

...JRF...

Re: /etc/resolv.conf

Steven Mertens — Wed, 17 Jul 2002 16:31:15 GMT

hi,

I assume no trouble if you change the
permission to 644.

regards.

Steven

Re: /etc/resolv.conf

RAC_1 — Wed, 17 Jul 2002 16:34:00 GMT

No problems with that. 666 is more open to users.

Re: /etc/resolv.conf

S.K. Chan — Wed, 17 Jul 2002 16:36:10 GMT

Mine's at 444 ( I suppose that's minimum requirement ) so changing it to a "wider" access permission should not have any "resolving" issues. 644 is OK, nothing more than that.

Re: /etc/resolv.conf

MANOJ SRIVASTAVA — Wed, 17 Jul 2002 16:37:58 GMT

Hi Joe

It should be set to readable only bcoz the system looks for the same , nay thing other tahn taht has its own weaknesses.

Manoj Srivastava

Re: /etc/resolv.conf

joe_91 — Wed, 17 Jul 2002 16:43:56 GMT

Thanks.

Joe.

Re: /etc/resolv.conf

papatot — Wed, 17 Jul 2002 23:27:35 GMT

If think 444 is OK! Beside edit it , users(include root) only read it when necessary.

papatot.

Re: /etc/resolv.conf

Bill Hassell — Thu, 18 Jul 2002 01:55:39 GMT

Just a note about system security. Every file *and* directory that is world writable cannot be trusted! The hacker's favority tool is the ability to change ordinary files into something else and for this, all that is needed is write permission to the directory or file. 666 and 777 are VERY bad permissions and when discovered, the affected files and directories should be carefully examined for content. The exceptions are /tmp and /var/tmp which must be 777 but more appropriately, 1777 (which requires the owner in order to delete or rename an entry in the directory).

The most common causes for bad permissions are:

- some process complains about permissions and a bunch of files are changed to 777 in hopes of solving the problem. Usually, it doesn't but the permissions are left open anyway.

- umask has never been set. This is an absolute requirement for every Unix system and must be set for every user as: umask 077 or slightly less secure, umask 022. Make sure umask is set in /etc/profile and /etc/csh.login

Re: /etc/resolv.conf

Balaji_6 — Thu, 18 Jul 2002 06:01:36 GMT

Hi Joe,

The sideeffect using 666 is the goup and other users in that machine can also modify /etc/resolv.conf file.

It is safe to have the permission as 444.
By default the permission for /etc/resolv.conf file is 644.

-Balaji