Bug 609832

Summary: system-config-users crashes or freezes if large number entered to uid and gid
Product: Red Hat Enterprise Linux 6 Reporter: Miroslav Vadkerti <mvadkert>
Component: system-config-usersAssignee: Nils Philippsen <nphilipp>
Status: CLOSED CURRENTRELEASE QA Contact: Miroslav Vadkerti <mvadkert>
Severity: high Docs Contact:
Priority: low    
Version: 6.0CC: mitr, pknirsch
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: system-config-users-1.2.100-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 610172 610838 616067 (view as bug list) Environment:
Last Closed: 2010-11-10 21:44:06 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:
Bug Depends On: 610838    
Bug Blocks:    

Description Miroslav Vadkerti 2010-07-01 09:20:26 UTC 
Description of problem:
When I enter a large number for UID when creating users (example 4294967296 - which is the maximum number by gui) s-c-users crashes. 

When creating a group with very large GID s-c-users freezes.

** ERROR **: lu_value_get_id(): value 4294967296 out of range
aborting...
/usr/share/system-config-users/system-config-users: line 4: 12766 Aborted                 (core dumped) /usr/bin/python2 /usr/share/system-config-users/system-config-users.py


Version-Release number of selected component (if applicable):
system-config-users-1.2.94-1.1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. launch s-c-users + enter root passwd
2. add user
3. add user name, password and select own UID as 4294967296
  
Actual results:
Crash

Expected results:
Error msg
Comment 18 Miroslav Vadkerti 2010-08-04 13:40:18 UTC 
VERIFIED as fixed in system-config-users-1.2.100-2.el6:
Maximal value accepted by s-c-users is now 4294967294
Comment 19 releng-rhel@redhat.com 2010-11-10 21:44:06 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.