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
This project is based on .NET Framework 4.7.2 and DevExpress v22.1.4. If you want to use it, you can directly download the compressed package below [Release](https://github.com/bodong1987/AHeadLib.Net/releases). To compile you need to install DevExpress.
12
12
13
13
---
@@ -21,7 +21,7 @@ This project is based on .NET Framework 4.7.2 and DevExpress v22.1.4. If you wan
Open the tool and select the dll you want to disguise in the first line.
26
26
The second line selects a directory. Then click Generate, it will generate a complete Visual Studio 2022 C++ project for you. If nothing unexpected happens, open the corresponding sln and you can compile it.
27
27
If you want to obtain other versions of the project, you can refer to the corresponding configuration and create a new project, or you can directly modify the vcxproj file to achieve your goal.
@@ -32,14 +32,14 @@ If you want to obtain other versions of the project, you can refer to the corres
32
32
第二行选择一个目录。然后点击Generate,它会为你生成一个完整的Visual Studio 2022 C++项目。如果不出意外,打开对应的sln就可以编译了。
Open the `UserImplementations.cpp` file. There are two user-defined methods. You can customize the original dll file path and append your own custom code in these two methods.
35
+
# Custom Process 自定义处理
36
+
Open the `UserImplementations.cpp` file. There are some user-defined methods where you can customize the original dll file path, decide whether to execute Patch code, and append additional custom code.
The tool provides a very simple Patch framework, which will search for segments according to certain rules when the hijacking dll is loaded, and dynamically replace the bytes that meet the requirements with the bytes you provide. There are two methods. One is to directly compile the `${LIB_NAME}_patch.txt` file in the Resource directory and configure it according to the rules inside;
44
44
the other is to create a new `${LIB_NAME}.patchconfig` file and place it with the hijacked dll. Together, configuration strategies and resources are the same.
45
45
for example:
@@ -54,9 +54,9 @@ Configuration rules :
54
54
;
55
55
; use ; start a comment line
56
56
;library : dll name with .dll extension or 0, 0 is the main module
57
-
;segenemnt : segment name, eg: .text|.data
58
-
;signature : hex byte value sequence, splitted by space
59
-
;newBytes : hex byte value sequence, splitted by space
57
+
;segment : segment name, eg: .text|.data
58
+
;signature : hex byte value sequence, split by space
59
+
;newBytes : hex byte value sequence, split by space
60
60
61
61
; for example:
62
62
;library : 0
@@ -87,9 +87,9 @@ Configuration rules :
87
87
;
88
88
; use ; start a comment line
89
89
;library : dll name with .dll extension or 0, 0 is the main module
90
-
;segenemnt : segment name, eg: .text|.data
91
-
;signature : hex byte value sequence, splitted by space
92
-
;newBytes : hex byte value sequence, splitted by space
90
+
;segment : segment name, eg: .text|.data
91
+
;signature : hex byte value sequence, split by space
92
+
;newBytes : hex byte value sequence, split by space
0 commit comments