FAQ
FAQ - PS Protector
The assembly can be loaded with the PowerShell Import-Module command. The protected module behaves identically to the unprotected psm1.
No, there will be no measurable speed difference.
The DLL behaves identically to the PSM1, no problems are to be expected. If the PSM1 runs without errors, the DLL will work correctly and not behave any differently.
The .NET Assembly is encrypted for the highest level of protection. This optimally protects the assembly against the use of .NET Decompilers, such as “Jetbrains dotPeek” or “Redgate .NET Reflector”. The PS Protector uses code protection and obfuscation:
- Advanced Anti-Debug and Anti-Tracer Protection
- Advanced Overload Renaming
- Anti-Reflection Protection
- Anti-Decompiler Protection
- Control Flow Obfuscation
- Constant Value/Array Encryption
- ILDASM Protection
- String Encryption
- Symbol Renaming
In addition, various security measures have been integrated to protect the module (for example, ScriptBlockLogging is not allowed). A 100% safety can not be guaranteed. However, we are converting our own modules with the PS Protector and rely on our product.
To protect the code, the module can not be loaded when PowerShell ScriptBlock Logging is enabled.
After purchase, you will receive an account with which you can use the software for 1 year. At the end of this year, the subscription must be renewed.
The subscription is valid for one user only. Every developer needs his own license.
Yes, the modules continue to work. After the license has expired, you will not be able to convert any new modules.