Are obfuscation and encryption alone enough to protect from reverse engineering and theft?
No. When applied together, obfuscation and encryption provide a reasonable level of protection for IP contained in .NET code. However, even when used together, these techniques alone still may leave IP vulnerable to reverse engineering and theft. For example, if the thief knows how the VM’s interpreter works, IP data can be easily accessed during runtime, as it is no longer encrypted. Fortunately, the HASP SRM .NET Framework Envelope offers additional features that make its protection the best available solution. What are the extra features that the HASP SRM .NET Framework Envelope provides to solve this problem? The first is that the HASP SRM .NET Envelope enables encryption at the lowest level of executable code – the Method level. This means that the developer can specify that individual Methods are encrypted separately and decrypted only at execution. The result is that smaller portions of code are exposed in memory for shorter periods of time, making the IP contained in the code f
