CryptoObfuscator

[OneQuestionOnly]

Hi guys,

I'm a .Net developer and I want to protect my code before I release my application to the market.

I've spend a few hours reading posts in this forum and I came to conclusion that a decent solution is using SmartAssenbly for obfuscation and CryptoLicensing to protect my application with a good license scheme.

I would like to ask your opinion about CryptoObfuscator since I can use it with CryptoLicensing and is much cheaper as a package.

Does CryptoObfuscator provides some decent protection???
Better or worse than SmartAssembly?

I say decent because you guys can crack everything. I try to stop the junior crackers :)

Thanks in advanced,
Steve

[OneQuestionOnly]

By not answering to my question I assume you either can't crack a protected assembly with CryptoObfuscator, or you never done it, so I feel sfe to use it.

Thank you guys.

[kao]

Well, what do you expect us to do? Search the whole internet to find a single file that's protected with it? Nobody uses CryptoObfuscator and there's a good reason for that.

From a quick glance - it will take 4-8 hours for experienced reverser, less than a week to medium skilled one. If you can provide your own crackme for test, I will gladly prove that to you.

And don't even get me started about "latest military strength, state-of-the-art cryptographic technology" that CryptoLicensing claims to be.

[omnious]

Perhaps you should focus more energy on making your application work 100% and be without bugs, instead of spending (wasting?) time on software protection.

Yes, I understand that you want to protect your so-called "intellectual property", but why bother at all. You do not have a board of directors, or share holders to report to, and need to make them feel good about their "investment" by adding some fancy software protection. And even then...

Just my 2c.

[Git]

Lets keep it nice and friendly people. We don't want personal slanging matches here.

Git

[bball0002]

[Please DO NOT quote whole messages]

Instead of waiting for our answers, you could have searched around the web and saw that CryptoObfusctor and CryptoLicensing 2009 and 2010 were cracked. It was as simple as making the method "IsTrial()" always return false.

But I'm glad you feel safe to use it.