e-m-b-a / emba

EMBA - The firmware security analyzer
https://www.securefirmware.de
GNU General Public License v3.0
2.49k stars 223 forks source link

Specify file system instead of firmware #1125

Closed lucky-zh closed 2 months ago

lucky-zh commented 2 months ago

Is your feature request related to a problem? Please describe. Can I use EMBA to directly specify the file system obtained by unpacking the firmware for analysis? Because some firmware is encrypted, specific decryption scripts are required.

github-actions[bot] commented 2 months ago

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.

To show your love for EMBA with nice shirts or other merch you can check our Spreadshop.

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

m-1-k-3 commented 2 months ago

Hi @lucky-zh

after extracting the firmware manually to a dedicated directory you should be able to just specify this directory as firmware path with the -f parameter.

lucky-zh commented 2 months ago

Okay, thank you. Maybe it would be better to add an explanation of the -f parameter in usage.

m-1-k-3 commented 2 months ago
-f [~/path]       Firmware path

it is the firmware path :) If you would like to improve ... PR are welcome