Red Hat Bugzilla – Bug 56850
Cannot insert groups with more than 16 caracteres
Last modified: 2007-11-30 17:06:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
You can create a user with more than 16 caracteres but you cannot create a
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a user
/usr/sbin/useradd -d /home/user userwithalotofcaracteres
( user and group were created )
2. Try to create a group
Invalid group name !!
Actual Results: Cannot create the group
Expected Results: It should create the group, since by using useradd it
I had a crash in the system, since I had a huge number of users in one
group ( I checked and this bug is already reported ). It erased important
information from /etc/group. Trying to recreate the groups by
using /usr/sbin/groupadd, I could recreate some of them and I had to
insert them manually.
I hit the same error. The relevant error looks to be this one:
Oct 13 11:55:47 pc5140 e-smith: groupadd: abc123abc-1-0-2-11 is
a not a valid group name
I delved into shadow-utils and found this code in chkname.c:
check_group_name(const char *name)
* Arbitrary limit for group names - max 16
* characters (same as on HP-UX 10).
if (strlen(name) > 16)
Whereas the user code is:
check_user_name(const char *name)
struct utmpx ut;
struct utmp ut;
* User names are limited by whatever utmp can
* handle (usually max 8 characters).
if (strlen(name) > sizeof(ut.ut_user))
char ut_user[__UT_NAMESIZE]; /* Username. */
#define __UT_NAMESIZE 32
I don't see any reason for the arbitrary 16 - groups names
don't get logged to utmp in any case.
I suggest bumping it to sizeof(ut.ut_user) (i.e. 32). Patch to
follow after testing.
Note: The 16 character limit still appears in
Created attachment 105218 [details]
Allow group names as long as user names instead of arbitrary 16
Patch attached. This works nicely for me on RH7.3
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.