How to identify and use filesystem from embedded device's firmware image. 1906

Hello Carl,

Yes, I did gunzip it, but I didn't look thorougt it all (Sorry). Sounds nice that you have a workaround to the problem.

Do you know which webserver it is using - e.g. test it by entering a page which does not exists. They might not have implemented custom error pages. If you find out which server they use you could checkout if there is any known errors in it which can help you to gain access to the box.

Also it would be worth the try to make a portscan e.g. with nmap to see if they are listning on any other ports.

Since there is clear text in the image file it seams like a disk image or parbreastion image. If it is a disk image you can not mount it like you already tried. The parbreastion table have to be removed first, and since we don't know the parbreastion type it might be a hard task to ditermen the size of it. A script using dd and removing 1 byte at the time and testing with the mount command could be worth the test.

You could also take a look on the magic cookie in the image file and se it makes any sense to you and google. :-) The 'file' command didn't know the type though.

Mogens

Carl Farrington skrev: