Bug 1043785

Summary:	Anaconda does not set up administrator users properly
Product:	Red Hat Enterprise Linux 7	Reporter:	Michel Alexandre Salim <michel>
Component:	sudo	Assignee:	Daniel Kopeček <dkopecek>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	pza
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-13 11:51:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michel Alexandre Salim 2013-12-17 07:32:33 UTC

Description of problem:
Fresh installation of RHEL 7 beta x86_64, with only a single administrator user created and root password not set. After installation is finished I cannot use sudo, which after rescuing the system turns out to be because the rule in /etc/sudoers allowing members of %wheel to use sudo is still commented out

Version-Release number of selected component (if applicable):
sudo-1.8.6p7-7.el7.x86_64.rpm

How reproducible:
Always


Steps to Reproduce:
1. Fresh install of RHEL 7 beta, with root password unset but an admin user defined
2. Boot the newly installed system
3. Log in and try to use sudo

Actual results:
Attempt fails, user not authorized. While user is in %wheel, the group is not authorized to use sudo

Expected results:
Attempt should succeed -- 

Additional info:
In sudo 1.8.8-1 as shipped in Fedora 20 (and presumably whichever version is default in Fedora 19) the default is for %wheel to be able to use sudo with password

Comment 2 Phil Anderson 2013-12-30 22:46:43 UTC

This got me as well.  It appears to be intentional (see bug 969373).  Just to confuse everyone, instead of using sudo we need to use pkexec on RHEL 7 by default.

Comment 3 Daniel Kopeček 2014-01-13 11:51:15 UTC


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