Description of problem: luseradd checks the length of login, but lusermod does not. Version-Release number of selected component (if applicable): libuser-0.56.6-2 How reproducible: Always Steps to Reproduce: # luseradd user-whose-login-has-34-characters Error creating group `user-whose-login-has-34-characters': name is too long (34 > 31) # echo $? 1 # grep user-whose-login /etc/passwd # grep user-whose-login /etc/group # luseradd user-whose-login # echo $? 0 # lusermod -l user-whose-login-has-34-characters user-whose-login # echo $? 0 # grep user-whose-login /etc/passwd user-whose-login-has-34-characters:x:501:501:user-whose-login:/home/user-whose-login:/bin/bash # grep user-whose-login /etc/group user-whose-login:x:501: # luserdel -r user-whose-login-has-34-characters # echo $? 0 # grep user-whose-login /etc/passwd # grep user-whose-login /etc/group user-whose-login:x:501: Actual Results: lusermod -l accepts login longer than 32 characters Expected Results: lusermod -l rejects login longer than 32 characters Additional info: This is a copy of fixed rawhide bug bz456267
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
*** Bug 646397 has been marked as a duplicate of this bug. ***
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification. Issue is already fixed in RHEL-6/7.