Enigma Protector

Hi, i recently protected my app using enigma 3.50.

but i have now found a cracked version of my app on the interent.

Can you tell me, does the 3.60 version have any significant changes from 3.50 that will stop the app being cracked.

Also when is you next update?

Thanks

Hi richyb,
Have you used control sum check-up and some anti-debuggers plugins?

Hi, thanks for the reply

Yes i use the control check sum, 2 options checked but hidden error message

an i had 4 plugins enabled

checkremotedebuggerpresent.dll
hardwarebreakpoints.dll
isdebuggerpresent.dll
isdebuggerpresentx.dll

its a .net app

Hi richyb,

Unfortunately, protection of .net files little different than just native executables.

For .net protection more features of protection should be used. The main advice is a better integration of main program and protection. If you will follow all my advices below, then I'm sure you succeed with a good protection.
1. For .net applications it is always recommended to use Virtual Box feature. Hide .dll dependences in it, or all other files.
2. Use different Enigma API functions. When you make a call to Enigma API, program refers to protection, if protected does not exist (file is cracked/unpacked) you will get an exception or unsuccessful result. For example, you may call functions like EP_CheckupIsEnigmaOk/EP_CheckupIsProtected and check if a result is true. If you are licensing or trial features, then use Enigma API to check license/trial status.
3. Use Protection Features - Protected Strings. Carry all strings from the code to protection, and extract necessary when it is needed. In this case, imagine if protection will be removed, no strings will be returned, and program will not work.
4. Use some unique protection techniques. For example, add a string in Miscellaneous - Environment Variable and check if it exists. If does not exist, then protection removed, then you should terminate application. Use delayed termination, i.e. not after check, but after few seconds.
5. If possible, carry some code to external dll with unmanaged code, and call this dll from .net application. You may protect dll with Enigma too with using of VM and RegCrypt markers, which provide good protection level.

Thank you for you comments. really helped alot.

Can i check something. if i bundle a file needed for the app to run with the protection. If it is cracked or unpacked say would they be able to extract the file i bundled in.

If not then the protection would work fine and make it uncrackable. if they can then i would need to use some other features.

Also some features you mentioned dont work for .net apps when i protect the app it wont run. i think this is due to being .net rather than your protection.

Thanks

It is better to combine all the features I described. Use as much of them as possible, not only one. As more you use, then stronger is the protection and it is more difficult to unpack the application.

richyb wrote:Also some features you mentioned dont work for .net apps when i protect the app it wont run. i think this is due to being .net rather than your protection.

Can you please let me know what features did you use and protected file did not work?

Enigma wrote:5. If possible, carry some code to external dll with unmanaged code, and call this dll from .net application. You may protect dll with Enigma too with using of VM and RegCrypt markers, which provide good protection level.

Please let me know, is it possible to apply encryption to a whole 3-rd party binary activex without source code and therefore without using markers? May be such bindings to freeware components could better protect a .NET assembly? At least it would make it harder to execute though would not protect from dumping assembly.

no any one protector uncrackable but make hard to crack for .net first protect with confuser then enigma it's very difficult to crack for new reverser
Best Regards
mdj