Crack Me.

[Andu]

@ LibX: Although I appreciate you offering and would want to know what you have to say in that regard I'm - as I already said several times - the wrong person as I'm not the developer of .Net Reactor.

@ All: There seem to be major changes in the current version that justify another look at the protection and maybe you will realize that it's not as bad as some of you think. But maybe I'm totaly wrong with this as I don't have the skills to verify or falsify this assumption.

I don't expect that anybody of you is going to take the challenge but if you do please post your experience.

[LibX]

Originally Posted by Andu

@ LibX: Although I appreciate you offering and would want to know what you have to say in that regard I'm - as I already said several times - the wrong person as I'm not the developer of .Net Reactor.

Yeah you just happend to be some random software developer hanging around on this forum for about 2 years asking over and over again about one and the same protection system we labeled "crappy" for countless of time but you just keep trying

And you keep saying over and over again after every cracked sample that you need to get some other protection system.....but you never do.
Could you please explain why?
And maby its really time to move to something better i totally agree but why do you need us to prove that for you over and over again? Its plain boring.

I want to add to this that i cant think of *any* software developer that keeps looking at a protection system like you do and even promoting it after witnessing countless successful cracking attempts thats just insane weird.

[Andu]

Originally Posted by LibX

Yeah you just happend to be some random software developer hanging around on this forum for about 2 years asking over and over again about one and the same protection system we labeled "crappy" for countless of time but you just keep trying

And you keep saying over and over again after every cracked sample that you need to get some other protection system.....but you never do.
Could you please explain why?

Well... of course I can. I'm developing a program in my free time for about 3 years now (no, not .Net Reactor but the program I'm going to protect). As I'm also interested in this whole protection 'game' I like to read in forums like this one. So what's wrong about asking you people what you think about certain protections? I know that you crack programs for the sake of fun and not to ruin software developers and that soft targets are not very rewarding.
Maybe my search for a capable protecion system looked like advertising to you. Let me assure you that this was never my intention.

Originally Posted by LibX

And maby its really time to move to something better i totally agree but why do you need us to prove that for you over and over again? Its plain boring.

Yes maybe but maybe not. In the beginning .Net Reactor protected programs may have been easy to crack but as I said I think that there was an evolution going on.

So if it is that crappy and if it is that easy then why don't you simply demonstrate it to us? Shouldn't take too long, right

And if you do you can be sure that I'll remain quiet.

PS: It was not me that brought it to the table again

[kao]

Hey guys, 1 month has passed and I'm curious if anyone has spent any time with FarJump's crackme..

@FarJump: since you are member of beta test program, do you have any information when official .NET Reactor 4.0 is coming out? I checked their webpage but there's no specific date given.

[Kurapica]

kao :

It's not wise to spend any time on the beta version, at least we want a full stable version to try, anyway I find the new SmartAssembly 4.0 more interesting to try, you should check it out.

[kao]

Ok, now that final version of Reactor 4.0 is out, I can post my solution to crackme (hxxp://www.mediafire.com/?rtdnnxyjmoj)..

There are some changes in protection code from 4.0beta to 4.0final but they are not that important. Approach used in my solution still works.
I did not write a full tutorial and most likely never will. The guys who already know how Reactor works don't need a tutorial. The guys who don't know should study it themselves.

Have fun,
kao.

[Kurapica]

very nice solution.

respect

[FarJump]

kao, is your patched exe intended to run? it crashes on all installed systems.

[kao]

@Farjump: Of course, it's supposed to run.
I couldn't make it crash on any system I have available (32bit XP/Vista English, different service packs, different .NET versions and hotfixes). Please, could you give info about your OS/installed version of .NET framework and hotfixes/exception text?

What I can tell you already:
1) Most likely it won't run on 64-bit machine/OS. Blame .NET Reactor for not setting Assembly flags correctly. Bug seems to be fixed in final release of Reactor 4.0;
2) There are some anti-debug tricks used by .NET Reactor, therefore EXE may not run under your favorite debugger/unpacking tool. Try clean PC instead;
3) I ignored certain parts of .NET Reactor code that are never used on my test PC. If that's the case, I'll gladly fix my errors.

Cheers,
kao.

[FarJump]

The exception message: "Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

As I only have x64 systems(XP/Vista/Win7-Beta) installed the problem could be related to the pre-jit feature which should convert small methods into native x86 code. I recognized not all small methods are converted to native code but probably enough to prevent ildasm-ilasm round trips. However, the original crackme works fine on my x64 systems.