Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 72657

Summary:	gdmsetup doesn't use same authentification as the other system configuration tools
Product:	[Retired] Red Hat Public Beta	Reporter:	Jan Sabbe <jan.sabbe>
Component:	gdm	Assignee:	Havoc Pennington <hp>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	null	CC:	nalin
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-08-28 22:28:31 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:
Bug Depends On:
Bug Blocks:	67218

Description Jan Sabbe 2002-08-26 13:27:06 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
You always have to type in the rootpassword when you start gdmsetup, even if you
started a redhat-config-program before.

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


How reproducible:
Always

Steps to Reproduce:
1.Start up Keyboard in system-settings:// and give root-password.
2.Start up Users & Groups in system-settings://, no need for the root-password.
3.Start up Login Screen

Actual Results:  You need to type in the root-password, even tough the keys in
the status area is still there.
	

Expected Results:  That it would start up without asking my root password.

Additional info:

Comment 1 Havoc Pennington 2002-08-27 21:16:05 UTC

hrm, the pam config file looks reasonable...

Comment 2 Havoc Pennington 2002-08-28 22:28:23 UTC

pam_timestamp needed to be before the pam_stack thing, I believe:

auth       sufficient   /lib/security/pam_rootok.so
auth       required     /lib/security/pam_stack.so service=system-auth
auth       sufficient   /lib/security/pam_timestamp.so

moved in 2.4.0.7-8, should solve the problem.

Comment 3 Jay Turner 2002-09-03 20:08:04 UTC

Fix confirmed with gdm-2.4.0.7-10.