11–20 of 27 posts
Many of these techniques were pioneered by games programmers. The idea was that games should be played, not cheated and the same reverse assembly tricks apply and so the same counter-measures apply as well. One game that I'm familiar with had a never ending Matroshka like structure where each pass through a decryption routine would yield just another pile of gibberish and another chunk of code. The game took a couple…
I love cruel easter eggs like that. It worked didn't it.
Many of these techniques were pioneered by games programmers. The idea was that games should be played, not cheated and the same reverse assembly tricks apply and so the same counter-measures apply as well. One game that I'm familiar with had a never ending Matroshka like structure where each pass through a decryption routine would yield just another pile of gibberish and another chunk of code. The game took a couple…
I have a guess, but after reading that, I would very much appreciate knowing what the game was?
1. https://www.blackhat.com/presentations/bh-europe-06/bh-eu-06...
https://www.pelock.com/products/obfuscator/screenshots
it does even more anti-re damage and it's been on the market for about 5 years?
Many of these techniques were pioneered by games programmers. The idea was that games should be played, not cheated and the same reverse assembly tricks apply and so the same counter-measures apply as well. One game that I'm familiar with had a never ending Matroshka like structure where each pass through a decryption routine would yield just another pile of gibberish and another chunk of code. The game took a couple…
Many of these techniques were pioneered by games programmers. The idea was that games should be played, not cheated and the same reverse assembly tricks apply and so the same counter-measures apply as well. One game that I'm familiar with had a never ending Matroshka like structure where each pass through a decryption routine would yield just another pile of gibberish and another chunk of code. The game took a couple…
Hmm why not just dump the mapped memory when it started up? Or did it do this even after loading?
40100E jz 401011
401010 call 8B4C55A0 | 401011 mov eax, [ebp+0C]
| 401014 mov ecx, [eax+4]
401015 dec eax
401016 add al, 0F | 401017 movsx edx, byte ptr [ecx]
401018 mov esi, 70FA8311 | 40101A
40101C
Many of these techniques were pioneered by games programmers. The idea was that games should be played, not cheated and the same reverse assembly tricks apply and so the same counter-measures apply as well. One game that I'm familiar with had a never ending Matroshka like structure where each pass through a decryption routine would yield just another pile of gibberish and another chunk of code. The game took a couple…
http://marionjy.loria.fr/wp-content/uploads/2015/10/codisasm...
50 levels is pretty low compared to what modern packers have; according to those slides, 100+ is not uncommon, hence the need to automate the process.