Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 75828

Summary:	umask of 077 causes wrong permissions on config files
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <udo.christ>
Component:	redhat-config-network	Assignee:	Harald Hoyer <harald>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-10-13 11:41:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2002-10-13 11:41:36 UTC

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:

Comment 1 Harald Hoyer 2002-10-14 08:47:49 UTC


*** This bug has been marked as a duplicate of 75091 ***