Ghidra Dependency Help

Question

Ghidra Dependency Help

yepitsbrian opened this issue 6 months ago · comments

Describe the bug
First time using emba, installed per instructions but first run ended by flagging Ghidra as a missing dependency.
Is this a build issue or am I doing something wrong?

To Reproduce
Steps to reproduce the behavior:

EMBA installation: sudo ./installer.sh -d
Use the firmware available here: any
Start EMBA with the following parameters: sudo ./emba -f [firmware]
additional steps: Fails during dependency checks
See error

...
GHIDRA - not ok
    Missing GHIDRA - check your installation

Some dependencies are missing - please check your installation
                                                                             
Looks like your docker container is outdated - please update your base image: sudo docker pull embeddedanalyzer/emba'.                                    
ERROR: 1                                                                     
emba_emba_quest_run_94222ed9f830
[-] EMBA failed in docker mode!
...

Expected behavior
Pass dependency checks

Screenshots
N/A

Desktop (please complete the following information):

OS: e.g. Kali Linux 2023.4
EMBA version: current master branch
Installation method: default with up to date docker image

Priority issue
Are you already a Sponsor? - N

Additional context

Tried docker pull, but it shows as current version (696ae51efee5)

github-actions · Answer 1 · Tue Dec 12 2023 00:18:27 GMT+0800 (China Standard Time)

Thank you for contributing an issue!

Welcome to the EMBA firmware analysis community!

We are glad you are here and appreciate your contribution. Please keep in mind our contributing guidelines here and here.
Also, please check existing open issues and consider to open a discussion in the dedicated discussion area.
Additionally, we have collected a lot of details around EMBA, the installation and the usage of EMBA in our Wiki.

If you like EMBA you have the chance to support us by becoming a Sponsor or buying some beer here.

This is an automatic message. Allow for time for the EMBA community to be able to read the issue and comment on it.

Michael Messner · Answer 2 · Tue Dec 12 2023 02:12:17 GMT+0800 (China Standard Time)

We have updated our Base Image last night. When have you pulled the repo and the docker Image? Probably they are out of sync

nootkroot · Answer 3 · Tue Dec 12 2023 04:22:46 GMT+0800 (China Standard Time)

Same issue here, just cloned from the master branch and pulling the latest docker image on the latest and completely clean Kali VM. Installation also seems like it went flawless.

Michael Messner · Answer 4 · Tue Dec 12 2023 04:34:51 GMT+0800 (China Standard Time)

Will check this tomorrow

nootkroot · Answer 5 · Tue Dec 12 2023 04:57:17 GMT+0800 (China Standard Time)

Seems like the path it's checking is ./external/ghidra/ghidra_10.3.1_PUBLIC/ghidraRun so it's treating it as a relative path instead of the correct, absolute path /external/ghidra/ghidra_10.3.1_PUBLIC/ghidraRun .

Michael Messner · Answer 6 · Tue Dec 12 2023 05:26:43 GMT+0800 (China Standard Time)

If this is the only dependency error you can try -F until we fix it

yepitsbrian · Answer 7 · Tue Dec 12 2023 05:32:23 GMT+0800 (China Standard Time)

We have updated our Base Image last night. When have you pulled the repo and the docker Image? Probably they are out of sync

I don't remember exactly, but roughly 1500UTC on 11 Dec. Repo then docker image immediately following.

If this is the only dependency error you can try -F until we fix it

Thanks. I'll give that a try when I have a chance later.