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

qemu emulation commands #1093

Closed farmmanic closed 3 months ago

farmmanic commented 3 months ago

Is your feature request related to a problem? Please describe. i rebuild firmware and would like to use the qemu command that was used during analysis

Describe the solution you'd like print the script variables to a qemu_run.sh file if it isn't already done somewhere.

Describe alternatives you've considered add the emulator commands to the database Priority issue hope to contribute Additional context I could do it but figured i should ask first

you guys rock.

github-actions[bot] commented 3 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.

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

farmmanic commented 3 months ago

nvm i found the function in L10_system_emulation.sh create_emulation_archive it activates if debug mode is set

m-1-k-3 commented 3 months ago

Hi @farmmanic,

create_emulation_archive should run on every emulation attempt that was able to get the emulation state to a point where the system enabled services reachable via the network. With DEBUG_MODE=1 every run (also if no network reachability could be detected) should create an emulation archive that you can use for further analysis. This mode usually needs much more disk space which is the reason for not auto-enabling it.