[C#] Kaiser Obfuscator - In Development

[AceInfinity]

After some thought, with my spare time over the next while i've decided to try my hand at my own Obfuscator :) Lets see how well this goes lol. This can actually be very tricky to accomplish, but i'm prepared to take the test.

I worked on the design so far, and i'm reading up on a couple program security blog posts here and there...

Should be good for the experience, but i've got some cool effects for the basics so far, i'm just planning on what the "end-goal" would be for my obfuscator, so i've chosen to have some basic options (not sure what they will be yet). If I make another one down the road, then i'll get a bit more technical with configurability.

All the icons you see were created by myself in Photoshop, including the ICO for the program executable, and every other is also going to be personally created by myself, just to make sure that everything about this app is my own works.

 

[tom982]

Wow, looks great Ace! I really like the logo.

Would you mind keeping us updated with how you get on with this? It sounds fascinating - I wouldn't even know where to start with obfuscation!

 

[AceInfinity]

Sure will, unfortunately whenever I plan stuff like this because I have nothing to do, it seems some external force; fate or whatever you believe in, decides it's going to throw new things at me for me to do lol. Now i've got access to RTI and Crestron, and i've got Crestron components I can play around with using SIMPL+ or/and SIMPL Windows... I just can't choose something and plan for the days I initially set from the start to prioritize my life's doings lol.

This is something that I do very well intend on completing though. I have many motivations that will force me to complete this, eventually. Learning, personal use, sharing source code to improve the blueprints for obfuscation I came up with, etc...

And to maybe help others too.

 

[Temmu]

why would u do that?
doesn't compiling code "obfuscate" it?

 

[AceInfinity]

Nope... Not at all. It can be decompiled back into pretty basic instructions fairly easily with .NET as it basically compiles down to CIL, there's programs out there like .NET Reflector which can easily translate the compiled binary down to IL or even back into a close representation of the .NET code in which it was compiled with. Obfuscation makes it more difficult to decompile it to see that blueprint, but not impossible. Obfuscation is good though as a preventative against decompilation for lazy people who don't feel like deobfuscating your program.

If I wanted, I could get it so that if you opened up my .NET app in a program like reflector, all you'd see is a bunch of junk, perhaps even Chinese characters if I wanted...