Protect the existing DLL

Issues related to VMProtect
Post Reply
RunninThruLife
Posts: 3
Joined: Wed Apr 15, 2020 5:46 pm

Protect the existing DLL

Post by RunninThruLife »

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:
  1. DLL_A
  2. DLL_B
    and...
  3. EXE_1
EXE_1 uses DLL_A and DLL_B. Both DLLs need to be protected. DLL_B references DLL_A.

What we think:
To accomplish this we:
  1. Create DLL_A
  2. Create DLL_B
  3. Complie DLL_A
  4. Complie DLL_B
  5. Protect DLL_A
  6. Protect DLL_B
  7. Reference Protected DLL_B in DLL_A
  8. Reference Protected DLL_A in EXE_1
  9. Reference Protected DLL_B in EXE_1
  10. Compile EXE_1
What we'd like:
  1. Create DLL_A using VMProtect SDK using Markers where needed
  2. Create DLL_B using VMProtect SDK using Markers where needed
  3. Complie DLL_A
  4. Compile DLL_B
  5. Reference DLL_A in EXE_1
  6. Reference DLL_B in EXE_1
  7. Compile EXE_1
It seems like the SDK is only telling the VMProtect exe where to protect instead of manually adding the functions in the GUI. Is that correct?

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:
  1. One that hasn't been protected.
  2. One that has been protected.
Is there anyway to rename a protected DLL so the same reference can be used?

Does this make sense?

Thank you in advance.
Admin
Site Admin
Posts: 2566
Joined: Mon Aug 21, 2006 8:19 pm
Location: Russia, E-burg
Contact:

Re: Protect the existing DLL

Post by Admin »

It seems like the SDK is only telling the VMProtect exe where to protect instead of manually adding the functions in the GUI. Is that correct?
Yes, it's correct.
Is there anyway to rename a protected DLL so the same reference can be used?
Yes can rename a protected DLL to the same reference without any limitations.
Post Reply