Ghidra Dependency Help about emba HOT 7 CLOSED

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.

from emba.

Will check this tomorrow

from emba.

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

from emba.

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.

from emba.

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

from emba.

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 .

from emba.

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.

from emba.