First of all, the file has
not been encrypted, but encoded. No matter what Fr4gg0r says. Secondly this kind of encoding is a little specific and I don't think there are many guys using it, so there's nothing useful to learn. To understand the hint better, you could do the following:
1. Open the older version of the hack in a hex editor of your choice
2. Find a stack of some null byte characters (means two nils on the left hand side)
3. Keep the address in mind
4. Open the newer version
5. Take a look at the address...
If you still don't have a clue what I am talking about, feel free to ask for the "ub3r, super duper hint"
// Edit:
Quote:
Originally Posted by drogii
rofl you fail..
|
lmao you is da man (wiv sum hooge ballz)..
Quote:
Originally Posted by schlurmann
You will never get a full original recovery of the source code. That's just not going to happen. I didn't say that there aren't a few good possibilities to recover bits of code and find out how the program works.
So please grow the fuck up.
How did you become a mod btw? All I see from you is german colloquial and kiddie flames...
|
You're still kinda wrong (regarding the first part, which doesn't have anything to do with mods' capabilities). It's possible to rebuild more than just particles of the source code, see al_j's post for further information.
Quote:
Originally Posted by Fr4gg0r
You dont call it coded you call it crypted and watch at the end of the code. You will often find there what it is crypted with and then you can search how you can decrypt it.
|
It's not being encrypted not to mention "crypted", but encoded.