Thanks,
We have 2 more queries:
1- We integrated vprotect_con in our built steps to protect out binary, however, upon running we receive this error
error while loading shared libraries: libVMProtectSDK64.so: cannot open shared object file: No such file or directory
Do we need to ship libVMProtectSDK64.so along with our binary or we can skip it somehow? our customer might have reservations about running external library along with our binary, any wayaround or safer way?
Also, if it's not possible to run the protected binary without libVMProtectSDK64.so, can we have static version of same library for Linux? We do not see it in SDK.
2- When we protected binary using vmprotect demo version, it displays a GUI pop notification Message box with text about vmprotect demo version.
Apart from that, we also see some other notification messages are displayed in the pop-up Message box for example, if we lock a function, a message box displays about permission/missing license when we reach that function during execution.
Our question:
- can we expect that demo pop-up will go away once we have licensed version of protect?
Can we totally disable all GUI elements such as message box somehow? we want our binary to stay totally independent of any GUI element after protection. Can we do that with vmprotect
regards,