Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 75091 - 600 -> 644 mode change really doesn't
600 -> 644 mode change really doesn't
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
: 75828 (view as bug list)
Depends On:
Blocks: 74873 81720
  Show dependency treegraph
Reported: 2002-10-04 07:18 EDT by Nicholas J Kreucher
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-04 05:44:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nicholas J Kreucher 2002-10-04 07:18:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
My /etc/sysconfig/networking/devices/ifcfg-eth0 file was mode 600, when applying
new settings in neat, it asked to change this to 644, i clicked "yes", however
it really didn't change the permissions on the file. neat kept asking to change
it to 644, but always failed to actually do so. i manually chmod 644 the file
and neat stop asking.

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

How reproducible:

Steps to Reproduce:
1. chmod 600 /etc/sysconfig/networking/devices/ifcfg-eth0
2. neat -> change something -> apply
3. click "yes" when it asks to change the permissions on the above file to 644
4. the permissions remain the same

Actual Results:  the permissions remain the same

Expected Results:  permissions change to 644

Additional info:
Comment 1 Radu Cornea 2002-10-09 21:27:32 EDT
For me, changing anything with neat resets the permissions on /etc/hosts and
/etc/resolv.conf to 600, so no programs trying to access netwok work anymore (if
run as normal user).
Comment 2 Radu Cornea 2002-10-09 21:33:51 EDT
I should add to the previous statement that it happends when I run the network
utility from the menu, and it asks for the root password. I could not reproduce
it when running from command line, as root.
Comment 3 Harald Hoyer 2002-10-10 06:04:19 EDT
ok, additionally, neat should set umask(0644)
Comment 4 Harald Hoyer 2002-10-14 04:47:43 EDT
*** Bug 75828 has been marked as a duplicate of this bug. ***
Comment 5 Harald Hoyer 2003-01-13 10:20:34 EST
new packages to test available at:
Comment 6 Harald Hoyer 2004-06-04 05:44:42 EDT
Closing due to inactivity. Reopen, if the problem is still existing.

Note You need to log in before you can comment on or make changes to this bug.