Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 28 Mar 2014 14:17:19 +0100
From: Szabolcs Nagy <>
Subject: Re: be able to break inheritance of LD_LIBRARY_PATH

* <> [2014-03-28 10:42:08 +0000]:
> For our software setup it is crucial (quite useful otherwise in general)
> to be able to specify the location of the dynamic libraries per binary/run
> _without_ the unconditional inheritance imposed by LD_LIBRARY_PATH.

why do you use LD_LIBRARY_PATH then?

> A very nice solution would be the ability to explicitely run a standalone
> dynamic loader, as implemented in both glibc and uclibc. We are heavily
> relying on this functionality.

what is a standalone dynamic loader and how does it solve the lib path?

if you mean a separate binary from, that does not matter much
(the loader and are interdependent on each other's internals
anyway, they are one logical unit even if in two separate files)

if you mean you can run '/lib/ binary' then musl can do the same

> As a simpler approach I might suggest simply being able to drop
> LD_LIBRARY_PATH as soon as it has been read. An extra environment
> variable as a flag would do.

if you dont control the environment you will have other issues
(eg with LD_PRELOAD)

if you do control the env then just unset LD_LIBRARY_PATH

> Compared to a standalone loader this lacks the ability to run
> a binary with a different version of the loader/musl but at least
> makes it straightforward and safe to freely specify where to find other
> libraries.

the loader is whatever the PT_INTERP says in the elf header of the
binary, so you can set it per binary, but in general you want it to
be the same everywhere so binaries are portable
(there ar no "different versions of the loader" in musl)

in case you do a lot of lib path hacks note that the path lookup is
different in glibc than in musl:

	1) DT_RPATH if no DT_RUNPATH is present (transitive)
	3) DT_RUNPATH (eg set with --enable-new-dtags) (non-transitive)
	4) /etc/ (except with -z nodefaultlib)
	5) /lib:/usr/lib (except with -z nodefaultlib)

	2) DT_RPATH (transitive)
	3) {interp}/../etc/ld-musl-arch.path or /lib:/usr/local/lib:/usr/lib

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.