Rummage is designed to work out-of-the box, without requiring you to make advanced decisions about specific code elements or configure obfuscations in ways that do not increase security. Start Rummage, select your assembly, click “Obfuscate now”.

First-class obfuscation
Rummage is simple on the outside but advanced under-the-hood. It is designed to be used without having to understand how our algorithms modify the program. We do not believe in security through obscurity. Rummage permanently removes information which helps attackers from your program, and we want you to be sure of this. This is why we’ve explained what each of our algorithms does and why.

Automatic handling of reflection
Reflection is what makes obfuscation hard. Improper handling of reflection can severely limit the usefulness of an obfuscator. And it’s easy for reflection to slip in without you even knowing – for example, through the use of C#’s dynamic keyword. All of Rummage algorithms take reflection into account. Rummage starts off by inferring which types and members are reflected upon and how, and subsequently makes use of this information to keep the transformations it applies safe.

Debug symbols support
Debug symbols (.PDB, or program database) are produced by compilers to help debug a program. These files contain additional information which maps information in the compiled binary to the program’s source code. Rummage understands this information, and carries it over through the obfuscations. This enables stepping through the obfuscated binary in the debugger, and allows obtaining stack traces with source code line information.

Home:

http://www.aldaray.com/Rummage/Features

Download:

http://www.ddlstorage.com/5rno534lm7sp/Rummage.Net.Obfuscator.v2.2.750.Cracked.by.yoza_UpK_.rar.htm
http://ul.to/vhiooxwz
http://rapidgator.net/file/1451163a97d3491dbf273d561ef34704/Rummage.Net.Obfuscator.v2.2.750.Cracked.by.yoza[UpK].rar.html