Red Hat Bugzilla – Bug 159035
'.' not allowed in usernames when creating new account
Last modified: 2007-11-30 17:07:18 EST
Description of problem:
s-c-users doesn't allow '.' in user/group names for new accounts. useradd does.
Please sync them up so people get consistent behavior. Here's what I think is
useradd's *intended* behavior:
* Wed Oct 27 2004 Adrian Havill <email@example.com> 2:4.0.3-23.04
- conform to posix for user/group name input checking [def 3.426
and 3.189] which is posix portable filename character set [3.276]
while disallowing dash for first char as recommended, and disallow
NOTE: The above is from RHEL3 branch and was broken in the next shadow-utils; I
hope that was not a change of mind but rather an error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a user in s-c-users containing '.' (eg: "joe.schmoe")
s-c-users won't let you do it ("Please do not use punctuation in the user name.")
It should work according to POSIX.
This issue is the same as bug #141273 in Fedora Core.
*** Bug 172106 has been marked as a duplicate of this bug. ***
NEEDINFO_PM has been deprecated. Changing status to NEEDINFO and changing
ownership to pm manager.
This would not have needed PM ACK as it is categorized as a bug.
A fix to this issue seems to be available and it is not unlikely that this
component will be included in a future Update release.
Moving to the next Update, clearing all ACKs.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
*** Bug 204292 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.