Incompatible with Windows 2008 R2 SP1 ENTERPRISE Ed

[sanyock]

It is a temporary measure related to source code security policy. And the process can recycle if needed periodically. We have not experience any instability for months of the protected program working; though on one server it just does not start because cannot find dotnet framework

[sanyock]

How can it have any reliability problems related to Enigma after unpacking IL into RAM and running on dotnet VM?

[sanyock]

And, I would have to assume all other types of protector programs would have the same compatibility issues.

Modern Themida Winlicense and sofpro.com do not have any problems at all.

About protection, I have not seen anything related to sofpro.com being hacked on public forums during the last 1-2 years.

On the other hand Enigma and Winlicense cannot survive even more than 6 months (actually Enigma only a one single day)
Though I think Enigma is good for money since it has not a fully automatic unpacker and has a full toolset included under $100/year.
Sofpro costs about 5-10 times more than Enigma and may be it is a price for reliability and may be for antihack protection since it is not hackecked itself for a long time.

I know Enigma provides some interfaces and suggestions to improve protection as a home work but other tools seem to protect just out of the box?

[Enigma]

May I ask why you would need to protect the server application? If it's running on your own dedicated server / vps, there should be no need to protect the files. It just seems a bit un-necessary since a server is meant to run 24/7, and may have some memory leaks when being packed and ran 24/7, especially under heavy load, I'm not sure if Enigma has tested it that thoroughly, it works fine for client applications. And, I would have to assume all other types of protector programs would have the same compatibility issues.

Enigma does not cause any memory leaks while protected application is working, so there is no any problems with it.

[perfectcode]

text removed

[sanyock]

If you leave the protector open for several days and use it to protect programs constantly, it will eventually say "Out of memory", and crash

IMHO:
It would be OK if protection tool could work at least about 1 hour without a crash or even a single protection pass and a serial number generation run.

Protection layer code is very different from the tool itself and the tool could crash for other reasons not related to being self protected, as I mentioned above other dotnet programs protected by Enigma work fine 24x7 for months without any crash caused by protection layer.

[Enigma]

In this aspect, protection of Enigma Protector itself does not cause memory leaks.

If there are memory leaks, then they are caused by the algorithm of protection process. While protection, there are allocated much memory and different objects, some of they may not free after protection finished.

But from version to version protection process is improving, and I'm not sure the problem exists with the latest releases.

[sanyock]

My problems seem to be resolved at last by the latest version of Enigma 3.120. It works fine with EazFuscator 3.6 which is able to virtualize even managed code. These two tools look like a very sweet couple

[sanyock]

And these two tools when used together seem to be much better than MS SLP which sometimes ago was priced about $50K

[Enigma]

Hi sanyock, thanks you very much for the very useful information!