Bug 98745

Summary:	pam_shells does not accept empty shell field in /etc/passwd
Product:	[Retired] Red Hat Linux	Reporter:	Andreas Luik <andreas.luik>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED UPSTREAM	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	srevivo
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-04 15:08:30 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:

Description Andreas Luik 2003-07-08 14:02:29 UTC

Description of problem:
According to the README.pam_shells file, if a login has an empty
shell field in /etc/passwd, "/bin/sh" is used.  Although we
have "/bin/sh" in our /etc/shells file, ftp logins are denied by
pam_shells when the login does not have a shell assigned in /etc
passwd.  Everything works well, when /etc/passwd is changed to list
"/bin/sh" (or "/bin/bash") in /etc/passwd.

How reproducible: always


Steps to Reproduce:
1. create login "x1" with empty shell field in /etc/passwd
2. try to "ftp machine" using login "x1"
3. observe, that it is not possible to login with ftp
4. it is possible to login with telnet, though
5. if the shell field in /etc/passwd is changed to "/bin/sh", ftp login is
allowed

Comment 1 Tomas Mraz 2005-02-04 15:08:30 UTC

The README was modified to reflect the reality in the upstream CVS.