VMProtect for ARM64 released
-
- Posts: 67
- Joined: Wed Jul 05, 2023 6:21 am
Re: VMProtect for ARM64 coming soon
soooooooooooooooon™, Any updates?
Re: VMProtect for ARM64 coming soon
Is there any plan to support VMProtect on other ARM64 OS like Windows ?
Re: VMProtect for ARM64 coming soon
VMProtect will support ARM64 for Windows, Linux and macOS.
Re: VMProtect for ARM64 coming soon
Hello,
I was very excited to see this announcement!
I am extremely interested in the ARM64 version and would like to ask if you have an estimated release date. I am ready to purchase it as soon as it's available.
If you are looking for beta testers, I would be more than happy to participate and provide feedback.
Could you also please share any information regarding the pricing model for the ARM64 version?
Thank you for your great work!
I was very excited to see this announcement!
I am extremely interested in the ARM64 version and would like to ask if you have an estimated release date. I am ready to purchase it as soon as it's available.
If you are looking for beta testers, I would be more than happy to participate and provide feedback.
Could you also please share any information regarding the pricing model for the ARM64 version?
Thank you for your great work!
Re: VMProtect for ARM64 released
The support of ARM64 was added in 3.10
Re: VMProtect for ARM64 released
is it supposed to work for Android arm64 native libs?
---
kind of... but after processing, llvm-strip gives:
and all the APK packaging seems to go wrong
---
kind of... but after processing, llvm-strip gives:
Code: Select all
error: section [index 1] has a sh_offset (0x8bd4e1edd9d13e7d) + sh_size (0x3d17aec82328b195) that is greater than the file size (0xccba78)
Re: VMProtect for ARM64 released
Dear VMP Team,
I hope this message finds you well.
I am writing to report a couple of issues I've encountered with the latest version of VMP when targeting the Android platform.
Firstly, it appears that the generated ELF files are not compatible with the Android linker, even when no virtualization features are enabled. The execution of a minimally protected binary results in the following error:
```
CANNOT LINK EXECUTABLE "/data/local/tmp/core_vmp": empty/missing DT_HASH/DT_GNU_HASH in "/data/local/tmp/core_vmp" (new hash type from the future?)
```
Secondly, I have identified that some specific instructions are not supported. The following BTI (Branch Target Identification) instructions, in particular, seem to be problematic:
```
9F 24 03 D5 BTI j
5F 24 03 D5 BTI c
```
Could you please advise if these are known issues or if there are any potential workarounds?
Thank you for your time and assistance.