I'm a software coder. I'm so confused. So hard to choose between Enigma Protector X64 or VMProtect... Which protector is more reliable ?

I'm coding for X64 platform !

Thanks.

I think VMProtect is better

I will go to VMProtect too.

So VMProtect for X64 is harder to crack no ? because X86 is somewhat easy to unpack (specially using scripts)

Edited January 14, 201510 yr by T-Mixer

Just keep in mind that if you dont use them properly, both are trivial to crack.

Just keep in mind that if you dont use them properly, both are trivial to crack.

No, I'm using the SDK + Markers.

Also I'm codinf for X64 that is harder than X86 to crack, because crackers are more familiar with X86 app.

Edited January 14, 201510 yr by T-Mixer

X86 is somewhat easy to unpack (specially using scripts)

Here you are wrong.

Each Protection have his unique features and if is well coded and projected it will be hard for a cracked to get trough.

This will be done in one day or another. It depends of interest.

My bet is to a system driver witch have access to ring0.

Well implemented will give you expected result.

Use UPX !

Use UPX !

 

Real funny DimitarSerg  

My bet is to a system driver witch have access to ring0.

Well implemented will give you expected result.

 

I disagree. Past few days I've been trying to write a kernel protection for my CrackMe, but what can you protect w/driver for anti-reversing purpose?

 

The stable kernel protection features do stuff like stop file deletion, hide file, stop process kill, stop registry key delete, block process/thread execution, disk crypto, and a few others - ie only designed to protect security softwares. 

 

IMHO kernel drivers are useless for anti-reversing (unless you have the kernel's source code and can mod/recompile it, which u dont for Win).

I think Safengine is better

It slows lots of your application response your SafeEngine.

And if you use the .NET protection is useless.

Edited January 17, 201510 yr by GIV

Your best protection would be to encrypt parts of the code or features you do not want people to use on a trial or demo version. Also using the same theory only release a demo version without the feature or code for a full version. Also many others also create fake registration keys that expire, or use a very cunning check against carders.. Make sure keys used are tied to the computer its for.. (in other words validate it as legitimate person buying it.. ) keep that in mind!

I disagree. Past few days I've been trying to write a kernel protection for my CrackMe, but what can you protect w/driver for anti-reversing purpose?

 

The stable kernel protection features do stuff like stop file deletion, hide file, stop process kill, stop registry key delete, block process/thread execution, disk crypto, and a few others - ie only designed to protect security softwares. 

 

IMHO kernel drivers are useless for anti-reversing (unless you have the kernel's source code and can mod/recompile it, which u dont for Win).

If you like to play around with that, I can suggest you to write a driver that can execute a certain function outside the user mode pe file. Its allways annoying but easily broken since you can allways disassemble the driver code.

If you like to play around with that, I can suggest you to write a driver that can execute a certain function outside the user mode pe file. Its allways annoying but easily broken since you can allways disassemble the driver code.

 

Thanks for suggesting, sure, even though I don't expect it to be difficult for you I will try that to see what happens.

latest "private exe protect" is better..

@RDGMax

bro reply

Use UPX

VMprotect or SafeEngine