Why empty in LD_LIBRARY_PATH be interpreted as `use the current directory`?

ronyweng ronyweng@synology.com
Wed May 8 07:20:00 GMT 2019



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?

 

 



More information about the Libc-help mailing list