Skip to content

Conversation

brianpow
Copy link

@brianpow brianpow commented Sep 11, 2020

remove 1000 images limit
fix typo in message
reuse image ID if the same firmware has been extracted before, improve error handling when extracting

@extremecoders-re
Copy link
Collaborator

Thanks for the PR!

Comment on lines +164 to +165
parser.add_argument("-s","--sql", dest="sql", action="store", default=None, help="Hostname of SQL server")
parser.add_argument("-b","--brand", dest="brand", action="store", default=None, help="Brand of the firmware image")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not using PostgreSQL database to store information about the emulated images.

From README,

Firmware Analysis Toolkit (FAT henceforth) is based on Firmadyne with some changes. Firmadyne uses a PostgreSQL database to store information about the emulated images. However just for the core functionality i.e. emulating firmware, PostgreSQL is not really needed. Hence FAT doesn't use it.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, FAT does not need it. I guess it won't harm to pass those parameter to firmadyne so user can use FAT even if they need the firmadyne sql feature/need to do some manual task with firmadyne later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants