Commonly used obfuscation encryption
If the algorithm is involved, the algorithm can be made into an unmanaged DLL
Is it true that C # can't really get something out of its own and not be finished by the Task Manager? Actually, I think that C # can do that. There are 2 reasons. 1,c# is a way to support the pointer with the * number. In other words, C # can use pointers. 2,c# can completely barrier-free call Windows own API functions (although the performance does not develop VC + +), call the third-party developed COM components, or even call the USB port Interface related information (roost do a U disk antivirus, used to, but mainly with the API to complete, An undisclosed API function R begins to forget). So, to this end, I am holding the confidence to start looking for a third party to provide dynamic link library and so on, after all, to write, C # still have a lot of performance and call problems to consider, after all, not graduation design, so, can be simple, as long as the above mentioned 5 ways to overcome the shortcomings.
Finally, Kung Fu is not a conscientious, find a half day, found a man named Peter, wrote a VC + + program to call VC + + dynamic link library, the implementation of VC + + program is not the end of the Task Manager source code. Fortunately, the source code is quite detailed (VC + + dynamic link library source code, VC + + application source), otherwise, the back of the way, there is no means to do. So I began, slowly, slowly embarked on the hard VC Code analysis. You might want to ask me what? I can very frankly tell you, although I VC ability is really not strong, but I want to put VC + + code, ported to C #. It sounds very unpredictable, but I really did. Finally, in order to repay my school-Chengdu Electronic Machinery College and Chengdu Institute of Information Engineering. I put VC + + application calling code, porting to. NET, and, for the convenience of invocation, I made it. NET can be recognized by the DLL Runtime library. Simply call run as follows. This DLL runtime can protect its own processes, or it can be set up to protect other processes, as a third-party dynamic link library exists. (Fortunately, although this third-party dynamic link library I still spend some time, but absolutely no charge, free broadcast, provide C # project source code download!) If everyone is interested also can discuss together, my mail is email:[email protected]), as for the cow man's design ideas, in fact, is to use the system function hooks, hooked up all the system function messages. There is no direct analysis of these things in Task Manager. However, in the CMD command console, the message cannot be accepted, so with the command console, you can end the process. However, the command console, the general user will not use, you can directly delete the command console, or ported to the program internal calls, not allowed to call outside the user, on the line. As for the other more troublesome things, you are interested in talking slowly.
Common tools:
DotNet Protector
. NET C # source code and credit Protection (code security)