dict object has not attribute 'iteritem' about firmadyne HOT 7 CLOSED

Hmm, is there anything in the objects table of the database? You can probably do:

• psql -h 127.0.0.1 -U firmadyne
• SELECT * FROM objects;

For the moment, you can probably skip the tar2db step. The only impact will be that the webAccess.py analysis won't work, because the database won't be loaded with the list of objects (e.g. files) in the tarball.

I'm currently traveling, but I'll take a closer look when I get back.

from firmadyne.

Sorry I'm not used to postgres. And I feel it's definitely a postgresql issue.

dyne/database├────
└┼─$─┤▶ psql -h 127.0.0.1 -U firmadyne
psql: FATAL:  database "firmadyne" does not exist

but...

└┼─$─┤▶ sudo -u postgres createdb -O firmadyne firmware
could not change directory to "/home/unknown/code/firmadyne": Permission denied
createdb: database creation failed: ERROR:  database "firmware" already exists

And you said I can skip step 5? But then it looks like I cannot continue because I need 1

└┼─$─┤▶ sudo ./scripts/makeImage.sh 1
[sudo] password for unkn0wn: 
Querying database for architecture... mipseb
----Running----
----Copying Filesystem Tarball----
Error: Cannot find tarball of root filesystem for 1!

Btw I also tried in a Kali Linux, then at step 6 I get

chroot: failed to run command ‘/busybox’: No such file or directory

But if I mount the image manually I see busybox is there

from firmadyne.

Sorry, I think I gave you the wrong PostgreSQL line earlier; it should be:

• psql -h 127.0.0.1 -U firmadyne firmware

Hmm, that's strange. Is there a 1.tar.gz file under firmadyne/images? For the issue you're referring to in Kali, the chroot is using busybox provided by your distribution (typically for x86 or x86_64), not any embedded busybox provided by the firmware. From a regular terminal, does which busybox provide a usable busybox binary?

from firmadyne.

Indeed that works with that command but the table seem empty. Gonna investigate this. And yes the .tar.gz is there. But I think I'll give up running this in my host, probably not the best idea if it modifies my network configuration.

So in Kali:

root@kali:~# which busybox 
/bin/busybox

from firmadyne.

Ok, thanks for the information. I tried spinning up a Arch system to check, but it's too different from Debian-based systems, so I don't think it can be supported without spending significant time on it, which I don't have. For example, it seems that ifconfig and vconfig have been deprecated in favor of ip in Arch, lots of dependencies like kpartx (multipath-tools) appear to be orphaned or unavailable in Arch, and binwalk doesn't support Arch either.

I'll take a look at Kali, but Ubuntu 14.04 should definitely work.

from firmadyne.

Ok, I've figured out the cause of the /busybox error. The package that needs to be installed should be busybox-static instead of busybox. Among others, I'm testing some fixes in the bugfix branch, those will be merged into master after I've tested them.

from firmadyne.

Indeed installing busybox-static fixed the problem and after a git pull everything works as expected (: thank you

from firmadyne.