Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

where possible, use rtld_audit instead of LD_LIBRARY_PATH #4

Open
serhei opened this issue Dec 11, 2019 · 2 comments
Open

where possible, use rtld_audit instead of LD_LIBRARY_PATH #4

serhei opened this issue Dec 11, 2019 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@serhei
Copy link
Owner

serhei commented Dec 11, 2019

'LD_LIBRARY_PATH considered harmful' is a common topic nowadays.

For oc-inject, LD_LIBRARY_PATH becomes a problem if the debugging tool spawns a process that needs to run in the container environment. Then the spawned process will use oc-inject libraries instead of the container environment's libraries, which is not what we want.

Probably necessary to use 'stap -c' with #2

@serhei serhei added this to the v1.0 milestone Dec 11, 2019
@serhei serhei added the bug Something isn't working label Dec 11, 2019
@serhei
Copy link
Owner Author

serhei commented Sep 14, 2020

Recent discussion about padding RPATH field to support RPATH editing, which might enable us to reconfigure the injected executable without too much fuss.

@serhei
Copy link
Owner Author

serhei commented Sep 14, 2020

Carlos O'Donell suggested using rtld_audit (la_objsearch) to override the library search path.

@serhei serhei changed the title where possible, relink the executable instead of using LD_LIBRARY_PATH where possible, use rtld_audit instead of LD_LIBRARY_PATH Sep 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant