This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: PATCH: ldconfig.c considers ld.so.conf entries before /lib,/usr/lib
> For setuid applications, the pathes /lib and /usr/lib are also special
> since glibc will not lookup any libs in the cache. Putting /lib and
> /usr/lib first will give the same libraries independ whether you're
> running setuid or not.
I just realized what this is saying. Why would it be setup this way?
This seems to be the actual reason that ldconfig is setup this way, but
I'm wondering _why_. What benefits are gained by setuid applications not
checking the cache?
Ben
--
.----------=======-=-======-=========-----------=====------------=-=-----.
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'