Bug 4419 - Username priveleges equivalent to ROOT PROBLEM
Summary: Username priveleges equivalent to ROOT PROBLEM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-08-07 16:56 UTC by walterh1
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-09-20 16:06:47 UTC

Attachments (Terms of Use)

Description walterh1 1999-08-07 16:56:56 UTC
First reported to Edgar in Calif. a couple of days ago.
I tried setting my user name password priveleges to be
equivalent to SU or ROOT.  It seemed to take but after about
two days approx up time I tried logging in as my specific
username, at the G U interface login screen ... It seemed to
want to take but reverted back to the same login screen and
after consistantly trying with my own login password I
couldn't login with the GU login screen always coming back
up.  Trying other usernames, I had no problems get into the
machine and trying ROOT no problem.  Switching into console
mode and logging into the machine with my username no
problem.  With Edgar's help we found that the system
wouldn't let me log in as USER and my priveleges set up
equivalent to ROOT (SU)..  THEREFORE changed all my username
priveleges back to non granted status; I am able to login as

Please return all comments to:


You people have done an excellent job with Red Hat Linux
keep up the good fight!

Walter Haiworonsky

Reformed and more the wise user.

Comment 1 Michael K. Johnson 1999-09-20 16:06:59 UTC
I don't know who Edgar is, so I can't ask him for details...

By default, we do not make linuxconf setuid root, and in that
configuration, the priviledges have no effect.

If that's not what you were doing, I'm sorry, but I can't
quite follow what you are saying.  I don't know what you
mean by the "G U interface login screen", for example.
If you are sure there is a bug here, you can re-open the
bug, but please include more explicit instructions on how
to recreate it (step by step) so that we understand what
you are trying to do and can better answer...

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