anyone re-engineered Reactor 4.x protection?

[chicken curry]

Hi, I'm also a software developer and i consider selling one of my programs. So I'm looking for a protection at least against tools that are easy to use and break everything in a few Clicks.

I read that Reactor 3.x was easy to crack by memory dump, but haven't seen any comments on Reactor 4.x
Has it improved?
If not, what makes {smartassembly} so good that you seem recommend it over the others?

Thanks in advance...

[bball0002]

Reactor isn't that bad. But, like any other jit hooking protector, the IL code is fully decrypted in memory. People recommend {SmartAssembly} because the obfuscation is good and it will stop most novice crackers.


But if you're app is that good, it will be cracked by someone no matter what protection you use.

[nzh]

I'm also interested in wether or not Reactor 4.x has been cracked and how it was done (moreso, how different it was from 3.x) for curiosity purposes

[kao]

There was .NET Reactor 4 unpackme somewhere on this board. I unpacked it but did not post full solution. There are no public unpackers for v4.x. LiBX got bored, so I doubt he'll make new version of Reziriz.
Protection has greatly improved compared to version 3.x. Code-flow obfuscation is quite good. All important data are encrypted and decryption key is based on strong name key token. There is some protection against JIT-hook unpackers but it's buggy.
Overall, it's not bad protection as it will stop most of the newbies. Pros will remove any kind of protection anyway.

[bball0002]

[Please don't quote whole messages]

It's been cracked, but I wouldn't go by that as most if not all protectors are cracked.

[chicken curry]

Well thanks a lot for your answers. :-)
I'll go for Reactor, because it also has a License Manager and smartassembly was a bit fuddly with a WPF app.