From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
This happens to me quite alot:

 When the umask is set to something "unexpected" like 077 as i have it 
 and the config tools are run under the user account (providing the root
password as needed) changes in the config files end up with the config files
having the access-permissions set to somthing like 600.
This of course disables stuff working. In fact i think it affects not only the
network config

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:

Have the umask set to 077

1. start network config as std user
2. provide root password
3. change - let say the DNS domains to look for
4. save and exit setup	

Actual Results:  The config files (resolv.conf, hosts) and such have a file
permission of 600 which stops the network access from working for the standard user.
The content of the files is ok.

Expected Results:  the files should have the permissions as before

Additional info: