📚 OpenRCE is preserved as a read-only archive. Launched at RECon Montreal in 2005. Registration and posting are disabled.








Flag: Tornado! Hurricane!

 Forums >>  Brainstorms - General  >>  Vxworks/zlib compatibility problems?

Topic created on: November 12, 2008 19:54 CST by rman .

Ive got a vxworks (5.5 specifically) device that Ive been working on off and on for a few months now while other projects are slow.  Have managed to get full disassemble of it, with a lot of the symbols, etc.

I've also found that I can edit some of the code for the firmware and upload it agian.  Thanks to a few of the guys around here and on the IRC channel we were able to figure out the checksumming for the "wrapper" file which contains a zlib compressed image of the code, and some of the webpages that it the device serves up, changing the checksums allows for changing the webpages, but now Im looking to edit the real code.

Seems like this should be relatively simple, but when I recompress the image without editing the code and put it back into the file it won't take the upload.  Im currently using the python zlib to compress it back, using Z_DEFAULT_COMPRESSION to deflate the edited file, which is what the original file was packed with (789c magic bytes), and I'm wondering if there are any known/common issues with this approach or any resources anyone could push me towards.  Have been struggling with this more than a little while today and would love to have my own code running on the device this week.

  aeppert     November 13, 2008 08:58.26 CST
Multiple things:

1) Is there a size value somewhere in the header, perhaps near the checksum?  If so, that will have to be updated, unless the sizes are identical.

2) Are you somehow damaging code after the zlib data?  I often encounter a prelude of sorts immediately after compressed data.  

3) Is there a specific checksum for the compressed data?  Sounded like there was for the wrapper, but there may be one specific to the compressed data.

Without seeing it, these are all just guesses of course.

  rman     November 14, 2008 16:52.23 CST
well Ill post a followup.  I bricked the damn thing, but had resigned myself that that was going to happen sometime in the process anyways.

More details at some point if/when I get it up and running again :)

Note: Registration is required to post to the forums.

There are 31,328 total registered users.


Recently Created Topics
[help] Unpacking VMP...
Mar/12
Reverse Engineering ...
Jul/06
let 'IDAPython' impo...
Sep/24
set 'IDAPython' as t...
Sep/24
GuessType return une...
Sep/20
About retrieving the...
Sep/07
How to find specific...
Aug/15
How to get data depe...
Jul/07
Identify RVA data in...
May/06
Question about memor...
Dec/12


Recent Forum Posts
Finding the procedur...
rolEYder
Question about debbu...
rolEYder
Identify RVA data in...
sohlow
let 'IDAPython' impo...
sohlow
How to find specific...
hackgreti
Problem with ollydbg
sh3dow
How can I write olly...
sh3dow
New LoadMAP plugin v...
mefisto...
Intel pin in loaded ...
djnemo
OOP_RE tool available?
Bl4ckm4n


Recent Blog Entries
halsten
Mar/14
Breaking IonCUBE VM

oleavr
Oct/24
Anatomy of a code tracer

hasherezade
Sep/24
IAT Patcher - new tool for ...

oleavr
Aug/27
CryptoShark: code tracer ba...

oleavr
Jun/25
Build a debugger in 5 minutes

More ...


Recent Blog Comments
nieo on:
Mar/22
IAT Patcher - new tool for ...

djnemo on:
Nov/17
Kernel debugger vs user mod...

acel on:
Nov/14
Kernel debugger vs user mod...

pedram on:
Dec/21
frida.github.io: scriptable...

capadleman on:
Jun/19
Using NtCreateThreadEx for ...

More ...


Imagery
SoySauce Blueprint
Jun 6, 2008

[+] expand

View Gallery (11) / Submit