Bug 7099 – klock problem with ypbind

Bug 7099 - klock problem with ypbind

Summary:	klock problem with ypbind

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-18 08:21 EST by Udo Jocher
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:	2000-02-18 06:52:21 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 Udo Jocher 1999-11-18 08:21:01 EST

Users, which account information is obtained by ypbind from another
machine, locking the terminal with klock are not able to unlock the
terminal. Giving the correct password, klock says "failed".
Users with a local account don't have this problem.

Comment 1 Bernhard Rosenkraenzer 1999-11-21 07:15:59 EST

Please check your PAM settings (/etc/pam.d/kde) and version.
Looks like a misconfiguration.

Comment 2 Udo Jocher 1999-11-22 13:06:59 EST

My PAM settings are (/etc/pam.d/kde)
#%PAM-1.0
auth       required     /lib/security/pam_pwdb.so shadow nullok
auth       required     /lib/security/pam_nologin.so
account    required     /lib/security/pam_pwdb.so
password   required     /lib/security/pam_cracklib.so
password   required     /lib/security/pam_pwdb.so shadow nullok use_authtok
session    required     /lib/security/pam_pwdb.so
session    optional    /lib/security/pam_console.so

My PAM version is pam-0.68-8

Comment 3 Bernhard Rosenkraenzer 2000-02-18 06:52:59 EST

Should be fixed in the current version.

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