Bug 98745 - pam_shells does not accept empty shell field in /etc/passwd
Summary: pam_shells does not accept empty shell field in /etc/passwd
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pam
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-08 14:02 UTC by Andreas Luik
Modified: 2015-01-08 00:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-02-04 15:08:30 UTC
Embargoed:


Attachments (Terms of Use)

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.



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