How do I best obfuscate my C# product license verification code?

Question

How do I best obfuscate my C#.net app Product Key verification code?

Is it enough to place it in a "INTERNAL SEALED CLASS CLASSNAME { };" or do I need to do more?

Thanks!

Answer 1

Access modifiers like internal and sealed don't have anything to do with obfuscation or code security, they just tell other classes how to interact (or not interact) with them.

At the end of the day, there's nothing you can do to prevent piracy. Anything created by one human can be broken by another. There are loads of questions on SO that deal with product keys, keeping software secure, etc. which you can find if you use the search mechanism in the upper-right. All the answers cover a few basic ideas that anyone with a little sense will tell you:

1. Only put enough effort into your anti-piracy measures to make cracking the software a little less convenient than breaking out the credit card. If that's really hard to do, you are charging way too much for your customer base.
2. If you focus on building positive relationships with your customers instead of assuming they are criminals, they will be more willing to give you money.
3. Most customers - individuals and especially companies - don't have any interest in cracking open your assemblies and trying to figure out how to get away with not paying you. For individuals, they wouldn't pay for it anyway so you're not losing a sale; and companies wouldn't risk mountains of cash in legal problems for the cost of some software licenses.

Research public/private and elliptic key cryptography and you'll find ways to secure your key algorithm, but it will only prevent cracking the key, not bypassing it.

Answer 2

Rex is correct, internal sealed class won't hide anything. Use a one-way encryption hash (e.g. MD5CryptoServiceProvider) to protect passwords and keys.

Answer 3

Use Microsoft Software Licensing and Protection service.

Software Licensing and Protection Services can help you protect, package, license, sell and control your software.

To protect your IP you can select certain functionality for one-way transformation, and this transformed code runs within a secure virtual machine (SVM), with each vendor receiving a unique SVM

Answer 4

I agree with Rex M, you should consider using an asymmetric encryption algorithm such as elliptic curves cryptography to avoid keygens. And if you are interested in a commercial solution then try Ellipter - it uses elliptic curves and has some useful features like product info and expiration data embedding into generated serial keys.

Answer 5

Making a class internal or sealed won't help your cause. The soure code can be viewed in Reflector anyway. You need to use an obfuscator such as Crypto Obfuscator. For product keys, use a licensing system such as CryptoLicensing.

Answer 6

we are not getting what u r telling in this. we want the answer directly pls provide