Quackster
a devbest user says what
- Aug 22, 2010
- 1,763
- 1,235
MonoShield
Because code is valulable.
Introduction
I am developing a program called MonoShield. It is called MonoShield because. (by .NET I mean C# and VB.NET applications)
1) It uses Mono.Cecil
2) It has the word shield because it protects your code.
This program can protect your code by..
1) Symbol renaming
2) Invalid method injection
3) String reference creation
4) String encryption
5) Anti-Reflector
All of these have been coded by myself!
What are these functions?
Good question. I shall explain. First off, symbol renaming makes all the classes with names to unreadable gibberish. This still makes the application work. But the names should only be kept for the coder and no one else.
From this:
To this:
--
The next task is invalid method injection.
Due to this. ILSpy breaks when you try to open the classes, but Reflector doesn't. Which is why I disabled the anti-reflector task.
And because nothing is returned, this will generate heaps of errors!
--
After that we have string referencing. This makes all strings are referenced to one class. And the method is called to get the strings
To
And when you click the method the strings are encrypted. String encryption is important as it prevents people from searching "password" or "license" as strings can be very sensitive and hold a lot of information.
--
And this is the anti-reflector included.
--
Because code is valulable.
Introduction
I am developing a program called MonoShield. It is called MonoShield because. (by .NET I mean C# and VB.NET applications)
1) It uses Mono.Cecil
2) It has the word shield because it protects your code.
This program can protect your code by..
1) Symbol renaming
2) Invalid method injection
3) String reference creation
4) String encryption
5) Anti-Reflector
All of these have been coded by myself!
What are these functions?
Good question. I shall explain. First off, symbol renaming makes all the classes with names to unreadable gibberish. This still makes the application work. But the names should only be kept for the coder and no one else.
From this:
To this:
--
The next task is invalid method injection.
Due to this. ILSpy breaks when you try to open the classes, but Reflector doesn't. Which is why I disabled the anti-reflector task.
And because nothing is returned, this will generate heaps of errors!
--
After that we have string referencing. This makes all strings are referenced to one class. And the method is called to get the strings
To
And when you click the method the strings are encrypted. String encryption is important as it prevents people from searching "password" or "license" as strings can be very sensitive and hold a lot of information.
--
And this is the anti-reflector included.
--
Right now this has been tested with multiple .NET applications. Every single application has worked except forms with images. Forms on their own work.
