Bug 103004
| Summary: | chsh to /bin/sh leaves shell field of /etc/passwd blank | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | UQ Business School <bugzilla> |
| Component: | util-linux | Assignee: | Elliot Lee <sopwith> |
| Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | ||
| 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: | 2003-09-05 17:36:37 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: | |||
Fix is in CVS and should appear in rawhide eventually. |
Description of problem: /usr/bin/chsh leaves the shell field of /etc/passwd blank, after the shell is changed to /bin/sh. In some ways this isn't a bug, since a null shell field is supposed to be equivalent to /bin/sh. But it seems strange for chsh to deliberately use null instead of /bin/sh. The vsftpd server will not run if the shell assigned to user "ftp" is a null string. This may be a bug, or it may just be acceptable level of paranoia. This problem was discovered when using chsh -s /bin/sh ftp Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. chsh -s /bin/sh someuser 2. egrep '^someuser' /etc/passwd 3. Actual results: last field of passwd is blank Expected results: last field should contain /bin/sh Additional info: