Bug 2815 – passwd without shadow doesn't seem to work

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 2815 - passwd without shadow doesn't seem to work

Summary:	passwd without shadow doesn't seem to work

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	pam (Show other bugs)
Sub Component:
Version:	6.0
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:	1999-05-14 04:26 EDT by flee
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:	1999-05-15 16:45:53 EDT
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 flee 1999-05-14 04:26:10 EDT

After upgrading from 5.2 to 6.0,
logins failed to work until I created a shadow
password file with "pwconv"

The messages from my syslog:

May 13 22:23:29 dacron-kangaroo-triptych PAM_pwdb[570]: get
passwd; pwdb: structure is no longer valid
May 13 22:23:30 dacron-kangaroo-triptych login[570]: FAILED
LOGIN 1 FROM (null) FOR flee, Authentication service cannot
retrieve authentication info.

Comment 1 Jeff Johnson 1999-05-15 16:45:59 EDT

I do not see this behavior (required pwconv in order to login)
on Red Hat 6.0 intel/or sparc. I also don't see the error message.

Check your PAM config in /etc/pam.d for the service that is causing
the problem. Perhaps you configured the requirement to use shadow
passwords sometime in the past ... ?

Please reopen with more information if you still think this is
a software problem.

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