Usually a cracker will make a patch in memory. From the feedback that I have from a cracker the software is quiet secure (with the existing protection-software) and memory patching would be the biggested opportunity to crack the software. The cracking scenario looks like this: The cracker creates a ...

But, program code can be patched in memory, and to avoid it, you have to integrate protection with the program as I wrote.

Also, protection of .NET program is specific, you can't use modern code protection - Virtual Machine (code virtualization) and any kind of markers. If you can carry out some ...

yes, I am interested in that. Please send manual and demo account. Thank you.

Thanks for that explaination!
I am also selling development components (only dlls) for SEO. Can dlls also be effective protected with Enigma?
At the moment I am using a competitor product for the software protection, that also uses hardware ID licensing, but it got broken with a byte patch. But we ...

hi,

at the moment I am protecting my C# software with a competitor product. But unfortunaly my software got cracked with byte patching with ollydbg.
Is Enigma Protector the answer for this problem? Does Enigma make a rock-solid protection against byte patching with tools like ollydbg (there are ...