News for hackers. Stuff that matters.

A comment on Using LD_PRELOAD to cheat, inject features and investigate programs (2013). Parent comment

Re:Using LD_PRELOAD to cheat, inject features and investigat... by theamk on Tuesday December 05, 2017 @12:27PM (#15853407)
Huh? It has not been rejected -- it is up to compiler/linker what to put in RPATH, and you can totally set RPATH to $ORIGIN. There is a nice tool, chrpath, to do so. For example, java sets it to:

    /usr/bin/java: RPATH=$ORIGIN/../lib/amd64/jli:$ORIGIN/../lib/amd64
I believe the reason it does not happen by default is that binaries go to /usr/bin, and no .so files should appear there. Also it breaks when hardlinks are involved.
[ Parent | on HN ]
Re:Using LD_PRELOAD to cheat, inject features and investigat... by AnIdiotOnTheNet on Thursday December 14, 2017 @01:44PM (#15925311)
> I believe the reason it does not happen by default is that binaries go to /usr/bin, and no .so files should appear there. Also it breaks when hardlinks are involved.

I other words, nobody uses it. So many conflicts could be easily solved if applications dropped this retarded insistence on spreading files over the hierarchy by type, but they just keep doing it because they mistake tradition for wisdom.

[ Parent | on HN ]