License Validation Protection

I implemented a C # build that checks the license for the application. The problem is to send this to the client so that they can easily find the keys that we use to encrypt the string.

Conclusion

Signing the application is a little painful because several of the components used are neither signed nor compiled. Therefore, we must manually parse and reassemble the snk file. Assembly loading is a chain reaction. I want to clarify that signing is only required to download assemblies directly? Do the assemblies downloaded further from these satellite assemblies also need to be signed?

Obfuscation

The public publication does not really mess up the lines. the code is mostly visible. Should I go for a professional publication?

I am completely new to this. Please, help.

+5
source share
1 answer

I would like to point out one problem that I'm sure you know when you are trying to protect your software. Since the computer that will run the application must be able to "see" all the code and data that you use, there will always be some way for other people to reverse engineer your application. All keys and secrets used to protect your software will be available as part of the data and assemblies that are sent ...

Conclusion

( ) , , , , , . , , . , - ( ) , .

, . , , . , Ilmerge, DLL, dll. . ilmerge .

Obfuscation

, , , . , , - Eazfuscator, . Eazfuscator .

. , , , . , ( ):

, , .

: " " Donationcoder.

+4

All Articles