You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,10 +15,10 @@ The library is:
15
15
- Very easy to use, with only 5 functions in its public interface
16
16
- Very flexible, with total fine-grained control over which techniques get executed
17
17
- Cross-platform (Windows + MacOS + Linux)
18
-
- Compatible with ARM architecture
18
+
- Compatible with ARM architecture and 32-bit Windows
19
19
- Header-only
20
20
- Available with C++11 and above
21
-
- Features up to 70+ unique techniques
21
+
- Features up to 80+ unique techniques
22
22
- Able to detect VMware, VirtualBox, QEMU, KVM, Parallels, and [much more](https://github.com/kernelwernel/VMAware/blob/v0.2/docs/documentation.md#vmbrand)
23
23
- Able to detect semi-VM technologies like hypervisors, docker, and wine
24
24
- Able to guess the VM brand
@@ -115,7 +115,7 @@ You can view the full docs [here](docs/documentation.md). Trust me, it's not too
115
115
> Yes. There are some techniques that are trivially spoofable, and there's nothing the library can do about it whether it's a deliberate false negative or even a false positive. This is a problem that every VM detection project is facing, which is why the library is trying to test every technique possible to get the best result based on the environment it's running under.
116
116
117
117
- Can I use this for malware?
118
-
> This project is not soliciting the development of malware for obvious reasons. Even if you intend to use it for concealment purposes, it'll most likely be flagged by antiviruses anyway and nothing is obfuscated to begin with. Good luck manually obfuscating 5000 lines of C++ code lmfao
118
+
> This project is not soliciting the development of malware for obvious reasons. Even if you intend to use it for concealment purposes, it'll most likely be flagged by antiviruses anyway and nothing is obfuscated to begin with. Good luck manually obfuscating 6000 lines of C++ code lmfao
119
119
120
120
- Why GPL 3.0 and MIT?
121
121
> I would've made it strictly MIT so proprietary software can make use of the library, but some of the techniques employed are from GPL 3.0 projects, and I have no choice but to use the same license for legal reasons. This gave me an idea to make an MIT version without all of the GPL code so it can also be used without forcing your code to be open-source. It should be noted that the MIT version removes **8** techniques, and the lesser the number of mechanisms, the less accurate the overall result might be.
@@ -147,6 +147,10 @@ And if you found this project useful, a star would be appreciated :)
0 commit comments