Bug 567 – glibc doesn't contain /etc/resolv.conf so it gets created with duff permissions

Bug 567 - glibc doesn't contain /etc/resolv.conf so it gets created with duff permissions

Summary:	glibc doesn't contain /etc/resolv.conf so it gets created with duff permissions

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	glibc (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1998-12-22 18:52 EST by Chris Evans
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1998-12-30 17:21:51 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Evans 1998-12-22 18:52:43 EST

Hi.

Freshly installed system.

/etc/resolv.conf isn't owned by any package. Instead it gets
created at some random time. Unfortunately it gets created
with mode -rw------- (only root can read).

This means that once DNS servers to use are defined, only
root can use them still!

One fix is to include a virtually blank /etc/resolv.conf
along with glibc, but making sure it has the correct
permissions (-rw-r--r--)

Comment 1 Jay Turner 1998-12-30 17:21:59 EST

After doing a fresh install on several test machine, each time the
resolv.conf file is created properly with the right permissions.

-rw-r--r--

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