Protect the existing DLL
Posted: Wed Apr 15, 2020 6:14 pm
Hello,
I'm new to this forum and to this software. Please excuse me if this topic has been discussed elsewhere. I've made an example below that illustrates how I believe we will have to incorporate the VMProtect software, and another example illustrating how we'd like it to work. Can someone please explain to me if I understand it correctly, and if it's possible to do what I'd like.
We have two DLL's and one EXE:
What we think:
To accomplish this we:
The GUI always seems to create a new DLL (DDL_A.vmp). As a result, we always have to re-reference the new protected DLL. That means we need two solutions:
Does this make sense?
Thank you in advance.
I'm new to this forum and to this software. Please excuse me if this topic has been discussed elsewhere. I've made an example below that illustrates how I believe we will have to incorporate the VMProtect software, and another example illustrating how we'd like it to work. Can someone please explain to me if I understand it correctly, and if it's possible to do what I'd like.
We have two DLL's and one EXE:
- DLL_A
- DLL_B
and... - EXE_1
What we think:
To accomplish this we:
- Create DLL_A
- Create DLL_B
- Complie DLL_A
- Complie DLL_B
- Protect DLL_A
- Protect DLL_B
- Reference Protected DLL_B in DLL_A
- Reference Protected DLL_A in EXE_1
- Reference Protected DLL_B in EXE_1
- Compile EXE_1
- Create DLL_A using VMProtect SDK using Markers where needed
- Create DLL_B using VMProtect SDK using Markers where needed
- Complie DLL_A
- Compile DLL_B
- Reference DLL_A in EXE_1
- Reference DLL_B in EXE_1
- Compile EXE_1
The GUI always seems to create a new DLL (DDL_A.vmp). As a result, we always have to re-reference the new protected DLL. That means we need two solutions:
- One that hasn't been protected.
- One that has been protected.
Does this make sense?
Thank you in advance.