Bug 106218 - useradd seg faults
useradd seg faults
Status: CLOSED DUPLICATE of bug 89145
Product: Red Hat Linux
Classification: Retired
Component: shadow-utils (Show other bugs)
9
All Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-10-03 14:44 EDT by Bob T.
Modified: 2007-04-18 12:58 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:58:55 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)
output of "strace useradd kde" (15.76 KB, text/plain)
2003-10-03 14:46 EDT, Bob T.
no flags Details

  None (edit)
Description Bob T. 2003-10-03 14:44:10 EDT
Description of problem: 
useradd (without -D) segfaults


Version-Release number of selected component (if applicable):
shadow-utils-4.0.3-6



How reproducible:
Every time, and on two separate RH 9 boxes


Steps to Reproduce:
1.useradd anything
2.
3.
    
Actual results:
Segmentation fault (core dumped)


Expected results:
new user


Additional info:
strace to be attached
Comment 1 Bob T. 2003-10-03 14:46:42 EDT
Created attachment 94918 [details]
output of "strace useradd kde"
Comment 2 Bob T. 2003-10-03 14:47:50 EDT
rpm -V shadow-utils  is empty
Comment 3 Bob T. 2003-10-07 10:35:39 EDT
After comparing my trace with the trace of a successful useradd on another RH9
box, I conjectured that useradd was incompatible with libsafe.  And indeed,
after unsetting LD_PRELOAD, useradd no longer segfaults.  But presumably there
is unsafe  
code in useradd, which is somewhat worrisome.
Comment 4 Enrico Scholz 2003-10-08 06:05:16 EDT
Sounds like a dup of bug #89145 (which has a patch)
Comment 5 Bob T. 2003-10-08 07:59:58 EDT

*** This bug has been marked as a duplicate of 89145 ***
Comment 6 Red Hat Bugzilla 2006-02-21 13:58:55 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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