VMProtect Software » Forum

You should switch off the option "Strip Debug Information". It seems "ld" uses the ".dynsym" section while linking.

Could you provide an example (original SO + .VMP file + main.c) that shows your problem?

Please notice that the demo version locks all protected binaries to the current HWID, so you are unable to check them on the end user side because the error "This application is protected with demo version of VMProtect and cannot be executed on this computer." will occur.

Do we need to ship libVMProtectSDK64.so along with our binary or we can skip it somehow? Don't need because VMProtect removes it from dependencies during protection. can we expect that demo pop-up will go away once we have licensed version of protect? The full version doesn't show such message at s...

You should read the user manual about serial number generators:
https://vmpsoft.com/vmprotect/user-manu ... generators

So you can implement own tool to make anything you need.

It's impossible to detect the system clock rollback without getting the real date from the Internet. We can recommenв to use VMProtectActivateLicense and the licensing system will also use the date from your activation server.

It seems you still don't understand what different between "file on a disk" and "module in the memory".

P.S. The topic is closed.

"Search in module" searches for watermarks in the process memory for selected module, so if you want to do it on Linux you should use "VMProtect for Linux".

You should switch off the option "Memory Protection".

Are you a registered user?

You should remove unused licensing functions from "vmprotect.go" (like VMProtectSetSerialNumber, VMProtectGetCurrentHWID, etc.) because the Go's compiler can't do that itself.

#cgo arm64 LDFLAGS: -L./ -lVMProtectARM64

Look at %VMProtect%\Include\Go

Please try the latest build.