This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Why empty in LD_LIBRARY_PATH be interpreted as `use the current directory`?
- From: ronyweng <ronyweng at synology dot com>
- To: libc-help at sourceware dot org
- Date: Wed, 8 May 2019 15:20:47 +0800
- Subject: Why empty in LD_LIBRARY_PATH be interpreted as `use the current directory`?
I know it was deliberately, but it seems to be error prone.
Some utilities(gvm in my case) change LD_LIBRARY_PATH like this.
export LD_LIBRARY_PATH; LD_LIBRARY_PATH="${GVM_OVERLAY_PREFIX}/lib:${LD_LIBRARY_PATH}"
There is no default LD_LIBRARY_PATH in most of systems,
It turn out that the empty (current dirctory) is appended to LD_LIBRARY_PATH.
I am concerned for the security. Shouldn't glibc just ignore empty?