Workflow for analyzing files on the Embark host

[willmccardell]

Hello!

Is there a supported or hacky approach for analyzing files that are on the Embark host itself? Sometimes for very large firmware files it will be easier to download them straight to the host from a URL, rather than downloading to local machine and them uploading to the host that is running Embark. A check through the documentation showed there wasn't such an approach.

Alternatively, If I run EMBA on the host manually against the firmware is there a way to import the results directory in to Embark? A stochastic parrot suggested putting the files in the /var/www directory of embark.

Thanks!

[github-actions]

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 EMBArk, the installation and the usage of EMBArk 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.

[BenediktMKuehne]

Hi,

I will update the wiki with the latest changes, thanks for reminding me.
We do have an API that you could use from the EMBArk host to do that.
doc: https://www.securefirmware.de/embark/
wiki: https://github.com/e-m-b-a/embark/wiki/API
otherwise you would have to use a browser on the EMBArk host system.

For the import thing we have the import export menu

you just have to zip the log folder contents into one file and upload+import that.

Sorry for the late response