Specify Library Path with analyzeHeadless?

[psparc82]

Hi,

I have an unpacked EXT4 root filesystem that I'd like to recursively analyze with the analyzeHeadless script.

The libraries each binary uses are under /lib or /usr/lib, how can I tell analyzeHeadless to use these library paths so it can resolve the symbols and automatically apply markup to the binaries that use these symbols?

Importing each binary in the UI and pressing Options... (before analyzing) lets you do this but I can't figure out how to do it with the analyzeHeadless script

Thanks!

[ryanmkurtz]

Ghidra 11.2, which hasn't been released yet, will support a -librarySearchPaths headless option, which will let you do what you desire. Are you able to build the master branch?

[psparc82]

-loader-libraryDestinationFolder <project path>

All of these are defined in support/analyzeHeadlessREADME.html

Thanks!

if I have multiple folders with libraries in then how can I define multiple -loader-libraryDestinationFolder paths so my libraries don't all end up in a single folder? Can I just pass the top level project path? I'm trying to preserve the directory structure of the filesystem I've imported (I don't want the libraries to be moved/copied anywhere)

I think I'm confused as to why Ghidra is copying libraries to other folders in the project when all I'm trying to do is guide Ghidra into finding the libraries for each binary it analyzes

Also, did you see the screenshots in my previous post regarding libraries being copied into binary folders?

[ryanmkurtz]

Unfortunately we currently have no way to direct new libraries to be saved to anyplace other than the 1 folder you specify. Would you mind making a new ticket asking for the ability to preserve the libraries directory structure on import? I agree that would be useful. Can you mention the symlink issue too...we need to handle that as well.

[psparc82]

Unfortunately we currently have no way to direct new libraries to be saved to anyplace other than the 1 folder you specify. Would you mind making a new ticket asking for the ability to preserve the libraries directory structure on import? I agree that would be useful. Can you mention the symlink issue too...we need to handle that as well.

#7430

[s0kil]

Does librarySearchPaths resolve symlinks? libc.so.6 -> libc-2.25.so?

[ryanmkurtz]

Not yet, but we are working on that.