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

libc.so detection is broken #204

Closed
Jamie-Landeg-Jones opened this issue Aug 21, 2022 · 2 comments
Closed

libc.so detection is broken #204

Jamie-Landeg-Jones opened this issue Aug 21, 2022 · 2 comments

Comments

@Jamie-Landeg-Jones
Copy link

Issue tracker

If any of these values are not included, the issue will be closed and not worked

Issue

You can't use "find /" to find the location of libc.so !

Not only does it take forever, it may still not produce the correct result, as it may find a libc that isn't the "live" version

Far more reliable and efficient to parse the output of (e.g.) ldd /bin/ls

$ ldd /bin/ls
/bin/ls:
        libutil.so.9 => /lib/libutil.so.9 (0x800254000)
        libncursesw.so.8 => /lib/libncursesw.so.8 (0x80026c000)
        libc.so.7 => /lib/libc.so.7 (0x8002cf000)

Debug Report

include the output of checksec --debug_report

n/a

Command run to produce the error

any

OS version and Kernel version

n/a

Debug output

Run the same command as above to reproduce the error but include the --debug flag

e.x checksec --debug -f /usr/bin/ls

n/a

@disconnect3d
Copy link

+1 on this. Running checksec under wsl is terribly broken and slow due to those find calls.

@sreschke80
Copy link
Contributor

My approach is an optional parameter to specify the search location of libc as file or path.
#206

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants