Bug 77154 - UID Limitations (think 16 bit uid_t) and its results
UID Limitations (think 16 bit uid_t) and its results
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
2.1
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Larry Woodman
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-01 15:57 EST by Jonathon M. Robison
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-01 15:57:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jonathon M. Robison 2002-11-01 15:57:29 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98; F-5.0.1SP1-
20000718; F-5.0.1-20000221)

Description of problem:
UID's above 50000 (I have tried from 52000 to 900000) or so fail to work, in 
that the home directory is show as owned by a numeric that ISNT the user's UID. 
In addition, programs like ssh (into the box) and sudo die w/o giving help for 
users whose UID is that high.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.install Default AS2.1 (we use a kickstart)
2.useradd -u 625625 tester
3.ls -al /home/ and see that tester's home dir is owned by a number around 34000
4. Now try ssh into the box from another one.
5. Give tester sudo access and try using it as tester
	

Actual Results:  sudo says "killed", and ssh won't let you in.

Expected Results:  able to execute sudo commands, able to ssh in.

Additional info:

This is on the default kernel. On my laptop, I used the kernel-i686.config and 
made my own kernel (to enable LVM). THAT kernel does not have this problem. The 
unmodified kernel on the Dell PowerEdge server does.
Comment 1 Jonathon M. Robison 2002-11-13 08:46:36 EST
This problem seems to be gone in the updated kernel, 2.4.9-e.9

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