Red Hat Bugzilla – Bug 306241
newusers creates users with negative UID and GID on x86_64
Last modified: 2010-03-30 04:13:40 EDT
Description of problem:
newusers creates users with negative UID and GID on x86_64.
I think it may be related with different UID of nfsnobody on x86_64 (it looks
like 2^32 -1)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create file with 3 lines in passwd format with empty UID and GID fields
2.execute newusers with that file
users with negative UID and GID
users with UID and GID in range 500-2^32
Created attachment 237611 [details]
This patch should solve negative UIDs and GIDs and also adds some tests of input data
Here is patch. Uses some features used adduser.c to avoid adding users out of
range <500; 60000>, so now you can have daemons with UID or GID 2^16 or 2^32 or
did you tried to push the patch upstream (as far as exists, can't find more than
Debian's QA page)?
It would be great to push it upstream guys.
Cool, thanks Peter, I thought it's already dead.
Michel, if you succeed pushing it upstream I'll do you QA-check for free then.
The upstream mailing list is kinda vital, do you know it's fixed in latest
Might be worth to insert a bug in their BTS in case it's unfixed upstream.
I sent info about this bug into the shadow mailing list... The problem with this
patch is, that it can't be applied to the current version, it needs to be
re-written to fit with the current version
Great! They have fixed it in 4.1.1 (quite differently than my patch - they
shared more code with adduser). It which will be released today.
Michal, you can check it now.
Nice, it's fixed upstream but I guess the patch in this BZ should be in future
obsoleted by backported one.
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 "?".
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 therefore 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.