[saun123]

From publisher :

Redgate's .NET obfuscator
SmartAssembly is an obfuscator that helps protect your application against reverse-engineering or modification, by making it difficult for a third-party to access your source code.

If your entire business rests on the IP embodied in your software or you don't want your C# or VB.NET code exposed internationally, then obfuscating your code becomes a necessity, not a luxury.

With SmartAssembly, you get a comprehensive set of obfuscation features, including name mangling, control flow obfuscation, strings encoding, reference dynamic proxy, and declarative obfuscation.



Key Features :

Name mangling
Changes the names of methods and fields to make it hard to understand their purpose.

Control flow obfuscation
Converts the code inside methods to 'spaghetti code' to make it difficult to see how the application works.

References dynamic proxy
Creates a proxy for calls to methods outside of your assembly to make it hard to find external calls.

Strings encoding
Encodes the strings used in your software to hide such information as passwords and SQL queries.

Resources compression and encryption
Compresses and encrypts managed resources to make them hard to understand, and to reduce the size of the assembly.

Pruning
Removes non-useful metadata to make the code harder to reverse-engineer, reduce the size of the assembly, and improve loading time.

Dependencies merging
Takes all the DLLs and merges dependencies into the main assembly, so you don't have to load lots of DLL files, and so that they can also be obfuscated.

Dependencies compression and embedding
Compresses and embeds your dependencies into your main assembly, simplifying the deployment of your software and reducing the size of your program.

Method parent obfuscation
Moves methods in your code by changing the class they are in, making it harder to understand how methods and classes relate to each other.

Strong name signing with tamper protection
Signs your assembly and helps to protect it against modification (the additional tamper protection is not available in the Standard edition).

Declarative obfuscation
Excludes a member from obfuscation using custom attributes directly in your code.


Screenshot :





Virus scan : https://www.virustotal.com/#/file/b6ee49.../detection

Download link : http://zipansion.com/u4qV

Run license generator in Sandbox or VM

Enjoy it, Buy it!

Enjoy my thread!

[mothered]

Not that there's any difference In detection between the two In this case, but as opposed to the archive, It's best to scan the executable.

https://www.virustotal.com/#/file/e57a4f.../detection

I haven't got the time at the moment, but I'll certainly test It In my VM when It (time) permits.
Thank you.

[saturn5885]

ok bro, but missing the password to unzip the zip file

[Cryogenica]

If you want to protect your code, don't use .NET in the first place. Most obfuscators can't protect your code from someone who actually has time on their hands, since the only effective thing obfuscators can do is rename things to useless names, pruning, and program flow changes (which can all be counteracted with a little patience). In security, there are 2 common types of threats: the naive attacker, and the sophisticated attacker. The naive attacker (the only attacker obfuscators can stop) are usually unable to do anything with what they learn anyway, while the sophisticated attacker will just get around your defenses.

Encryption is useless (just take Java bytecode encryption, for example), since you have to decrypt the data anyway before using it, the same with string encoding. A proxy for references just pushes things up a level (now they just take a look at that proxy's code, too), and method parent obfuscation can be conquered by looking at what calls what, then just reorganizing things yourself. Name mangling and dependency merging only work until the attacker learns to read code fluently. Signing is good until someone realizes Windows doesn't require applications to be signed. Someone could remove the signature, then modify it, and most users won't know the difference. The attacker could even re-sign the application if they had access to a key Windows recognizes.

There's nothing wrong with obfuscation, but never rely on it. It will ultimately let you down if someone clever gets a real reason to peek into the code.

[skrtja]

Thanks for the share! I'll use this for when I write code.

[Vultra]

Thanks for sharing this interesting thread of yours

[sitazotetu]

Work like a charm!
Thanks for helping our community!

[mothered]

but missing the password to unzip the zip file

Upon opening the archive, the password Is on the right pane.

[saun123]

Yeah, Thanks password in zip itself!

[yejuvera]

Thanks bro, downloaded and work great with my dotnet project!