Bug 846772 - Sudo update b0rks localhost resolving completely
Summary: Sudo update b0rks localhost resolving completely
Keywords:
Status: CLOSED DUPLICATE of bug 846631
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sudo
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Daniel Kopeček
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-08 16:06 UTC by Mario Mikocevic
Modified: 2012-08-09 09:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 09:45:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mario Mikocevic 2012-08-08 16:06:14 UTC
Description of problem:

Updating sudo to latest
sudo-1.7.2p1-14.el5_8.2
b0rked server to inability to resolve any local name

ie
/etc/hosts
127.0.0.1  localhost testname

some programs cannot resolve that anymore like php, python scripts
but interestingly ping(8) works.

I resolved this by
yum remove sudo
yum downgrade glibc glibc-common nscd
yum update glibc
yum install sudo

and now local name resolving works.

Comment 1 Mario Mikocevic 2012-08-09 09:43:04 UTC
Found the culprit, upgrading sudo changes file permission of /etc/nsswitch.conf from 644 to 600.
It happens only on x86_64 arch.

Comment 2 Daniel Kopeček 2012-08-09 09:45:34 UTC

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


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