hello List:
Wolfgang suggested:
JD wrote:
Does anybody got fresh ideas ?
Maybe firmware is not (just?) encrypted but (also?/only?)
compressed?
the firmware could be laid out like this:
FIRMWARE LAYOUT
------------------------
loader_start: | firmware loader |
| uncompresses/ |
| decrypts firmware |
firmware start: |........................|
| |
| compressed/ |
| encrypted |
| firmware |
| |
------------------------
a few points about this:
- you need to find out where control is transferred first,
what is the entry point for the loader;
- then, you do not need to uncompress/decrypt the second part.
instead, all you need to do is to ensure that it gets copied
properly and that the loader can access it correctly to do
its decrypting or decompressing.
- there is one problem: whether you need to relocate the second
part and whether the firmware is relocatable and uses relative
addresses.
i hope that this is helpful.
Aaron
--
{ too much injection }
_______________________________________________
Linux4nano-dev mailing list
[email protected]
https://mail.gna.org/listinfo/linux4nano-dev
http://www.linux4nano.org
