[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nscd returns random login when UIDs are shared (glibc 2.2.5)

From: Marc MERLIN
Subject: Re: nscd returns random login when UIDs are shared (glibc 2.2.5)
Date: Mon, 8 Apr 2002 21:06:31 -0700
User-agent: Mutt/1.3.25i

On Mon, Apr 08, 2002 at 08:41:45PM -0700, Ulrich Drepper wrote:
> > Is this a bug?
> No.  If you cannot decide what ID 0 maps to how should nscd.  Pick one.
As you know, if you use the password file without nscd, a login lookup per
UID picks the first entry in the password file, so 0 maps back to root.
This works fine when you only use the password file.
> > Is there  a workaround,  i.e. a  way to have  nscd not  cache UID  0, or
> > always map it back to the first entry in /etc/passwd?
> The work-around is to fix your passwd file.

It's not broken :-)
It's a quite common sysadmin practise  to not give the root password around,
and to have several root accounts named after the sysadmins.
This works very well on all unices, but indeed, it breaks with nscd since it
apparently uses a table that maps 0 back to whatever the last login to uid 0
lookup was.

I'll agree that it's  not a bug in nscd, this behavior  is apparently due to
the implementation, which assumes that there  is a one to one mapping (which
is true most of the time).
So let's try something  different: is there an easy way to  tell nscd not to
cache uid 0, with a config option I do not know or a small patch, or does it
more or less require a big code change?

Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/   |   Finger address@hidden for PGP key

reply via email to

[Prev in Thread] Current Thread [Next in Thread]