Need Sudo help - uid does not exit in the passwd file

[Laurie A. Krumrey]

Hi All my virtual-techie friends,

I have mv sudo set up exactly the same on all
my boxes. Yet on this R390 HPUX 11.0 I am
having problems:

MOONLITE [/home/lkrumrey] # sudo clear
sudo: uid 102 does not exist in the passwd file!

My uid is 102 and yes it does exist in the
password file.

My visudo file is the same on all the servers.
I think I either made a silly mistake or
the 3rd party vendor software for web access
and taken over my box.

I also get this werid message I never saw before:

Moonlite [/home/lkrumrey] # whoami
Intruder alert.

Any clues???
thanks,
Laurie

[Uday_S_Ankolekar · Accepted solution]

Hi,

Try re-creatig your ID with UID 102..

Goodluck
-USA..

[James R. Ferguson]

Hi Laurie:

Check the permissions on /etc/passwd. They should be should be "-r--r--r--". I'll bet they're not!!!

Regards!

...JRF...

[Sanjay_6]

Hi Laurie,

If it possible that you are having the same UID for more than one user and your username come after some other username who shares the same UID.

hope this helps.

Regds

[John Payne_2]

My guess is that sudo can not read the /etc/passwd file. chmod 444 should work, but you also should ensure that it is owned by root and root. Also, is sudo currently running as (owned by) root on this box?

[Patrick Wallek]

Try running a 'pwck' on the problematic system. See if it turns up anything.

I would susepct either permissions, as JRF suggested, or duplicate UIDs. I think permissions though with the error you are getting.

[harry d brown jr]

Also, check your /etc/passwd file to make sure it isn't corrupt. Also the permissions on su need to be "-r-sr-xr-x".


live free or die
harry

[Sanjay_6]

Hi Laurie,

Are you using NIS+. Here is a thread from SUDO site.

http://www.courtesan.com/pipermail/sudo-users/2000-November/000427.html

hope this helps.

Regds

[Sachin Patel]

Hi Lauri,
I am trying to look this at different way. Are you using NIS for passwrod?
Check your /etc/nsswitch.conf file for that.

Sachin

[Laurie A. Krumrey]

OK the /etc/passwd file is fine (r-r-r and with root and sys) just like all my other passwd files on my other servers.

And there is only uid 102 and that is me, but
it happens for my two backups login as well,but
their uid's show up.

Sudo is not a login and I have the right permissons on this file.

We are not using NIS+, we have a trusted system
but so are all my other boxes. I will try for
kicks to delete and re-add my account.

Laurie

[Laurie A. Krumrey]

OK this may be it:

On my problem server I have these perms:

-r-sr-xr-x 1 root bin 24576 Aug 6 1998 su

On my good server I have this:

-r-sr-xr-x+ 1 root bin 24576 Aug 6 1998 su

Maybe I need that plus sign +...
laurie

[James R. Ferguson]

Hi (again) Laurie:

OK, make sure that the permisssions on /etc are 555 bin:bin.

I agree with Patrick, too, run 'pwck' on your /etc/passwd file to see if anything is amiss internally.

Regards!

...JRF...

[Laurie A. Krumrey]

Thanks All,

Uday's response to delete and recreate my account worked, tho I am not sure why.

the pwck did not find any problems...This is
a new box, maybe I added my account and then
converted to a trusted system..I'm just shooting in the dark here..but it works so the
ends justify the means, who cares if it works.

Sudo Lives!
Laurie

[John Payne_2]

Was this system created from an Ignite image? If so, did you include /home in the image? I have done this and ended up not owning my own home directory after our third party security tool created my account. Just an idea. (I am ALWAYS interested in the why....)

[Laurie A. Krumrey]

No I didn't use ignite. But I did notice
the env variables for PWD was not setup to my
home directory but /etc. I can't log back
into my server now to check (NIC problems -
don't you just love new servers)...

I think the 3rd Party Vendor stuff is messing
with stuff, but of course they would never
admit any problems.

Laurie

[CA1171300]

Had same problem, finally we revealed that /tcb/files/auth/system/pw_id_map was corupted, simple vipw and save the file had resolved this issue.