louemusic123 wrote: ↑Mon Jan 15, 2024 4:30 pm
I read manual in section "Markers Reg_Crypt" and see "after the module is protected, the code inside the begin/end markers will be encrypted and the ...", my interpretation is all markers not only vm(risc) can auto encrypted not only Reg_Crypt, is it?
VM/VMRISC markers are not encrypted, they are processed into PCODE that runs on a virtual processor. This is a different kind of protection, which provides the maximum security for protected code.
Reg_Crypt code is encrypted, that's right. It is being decrypted only if there is a valid license key and key unlocks necessary section.
Unreg_Crypt also encrypts the code, and protection decrypts it at start if conditions are met.
louemusic123 wrote: ↑Tue Jan 16, 2024 3:14 pm
Got it. but i wish my code section first in virtualized processing, then encrypt it again, can i complete it?
This is how it really does, if I've understood you correctly.
Protection first virtualizes markers/functions from map files, removes them from a code and then compresses/encrypts this code section.
Then compile this project with X64 platform in XE12. I use enigma X64 with a new project, simple select virtual box and select registry virtualize then
Process file. when click button event, it popup an error :
---------------------------
proj1_protected
---------------------------
Failed to set data for 'MyStringKey'
---------------------------
OK
---------------------------
It is good in X86 version. TEP is 7.4 X64 demo version
Virtual registry has some disadvantage, all the changes you make to virtual registry keys are being discarded after application restart. So even if you write something in this key, this value will be saved only during protected process works, after restart it won't exist. Apart of that, files virtualization allows to store changes using Storage function, just for your information. Registry virtualization does not have Storage function yet.
If possible, please attach your non protected exe file to this post, I will check it out.
emm.. it's not essential..
I eccount this error is in chance up just had a requirement, read and write some registry key / values but not present it to real registry, thuses may prevent some sniffers, and can keep system clean.
It's not important , byt the x64 virtual registry eccounter an error , so i report for this information
i run this code also in 32, 64bit, none protect, and protected process in times, only 64 protected file has a popup.
Because of forum upload restriction, you will delete the last ".7z" extention when files downloaded