otool addresses
otool addresses
- Subject: otool addresses
- From: "Martin Redington" <email@hidden>
- Date: Mon, 1 Sep 2008 03:05:28 +0100
Not an Xcode question as such, but this list seemed to be the most
likely forum to get a reply from ...
I've got an original binary, and a cracked version. I am the original author.
If I dump the two binaries with od, and diff the output, I can see
that a few bytes have been changed in two locations, and I have the
addresses for those locations.
I can see the most likely method call for hacking (to make the
cracker's job somewhat easier, I named the method something like
checkRegistration), which funnily enough, is called from two different
locations.
But, when I run "otool -otV" on the binary, the addresses I see (after
the hex->octal conversion) don't match up to the locations of the
changes I'm actually seeing in the binary.
So, to get to my actual question ...
When I'm looking at the otool output, do the offsets represent
absolute offsets within the binary, or to some kind of internal point
of reference (e.g. the start of the objective-C segment)?
Assuming that they are not absolute offsets (in the otool output), how
can I convert from the otool output to actual offsets in the binary,
or vice versa.
cheers,
m.
--
http://www.mildmanneredindustries.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden