My .NET Application Hacked. What to Do?
So, your application is popular and it got the first hacks. Congratulations on being awesome but this also means you probably have a constant flow of headache since then.
So, your application is popular and it got the first hacks. Congratulations on being awesome but this also means you probably have a constant flow of headache since then.
I was amused to find out that .NET assemblies can do native DLL exports with one and easy trick:
.method static void Rainbow()
{
.export [1]
ldstr "Rainbow"
call void [mscorlib]System.Console::WriteLine(string)
ret
}
That's a question I was asked for a long time in the past and I have a good answer now. First of all, it depends on what you want to achieve. If you are a hobbyist and want to pinch some pennies then shared web hosting will work quite well…
Eazfuscator.NET is a production tool. This means a lot of people rely on it every day. That fact puts a great responsibility on us.
Eazfuscator.NET has hundreds of automated tests. Nearly everything is tested: obfuscation impact on serialization, reflection, code semantics, user interface etc.
User interface (UI) testing turned out to be a twilight zone of computer science. That's why we had researched and developed a testing technology for user interface that is based on artificial intelligence (AI). And I think it will amaze you.
Recently I was working on some changes aimed to achieve better usability experiences for Eazfuscator.NET. One of the common pitfalls is the requirement to restart Microsoft Visual Studio after the first Eazfuscator.NET installation. This requirement is commonly addressed by a message box during installation asking user to restart the running…