Bug 609832 - system-config-users crashes or freezes if large number entered to uid and gid
Summary: system-config-users crashes or freezes if large number entered to uid and gid
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-users   
(Show other bugs)
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Nils Philippsen
QA Contact: Miroslav Vadkerti
Depends On: 610838
TreeView+ depends on / blocked
Reported: 2010-07-01 09:20 UTC by Miroslav Vadkerti
Modified: 2010-11-10 21:44 UTC (History)
2 users (show)

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)
Last Closed: 2010-11-10 21:44:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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
/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):

How reproducible:

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:

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.

Note You need to log in before you can comment on or make changes to this bug.