chenx221/Textractor_test
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
测试合并
314 Commits 1 Branch 0 Tags 21 MiB
C++ 98.1%
C 0.8%
CMake 0.7%
PowerShell 0.2%
Inno Setup 0.2%
679317b5f5
Go to file
Akash Mozumdar 679317b5f5 bugfixes
2018-08-23 13:15:24 -04:00
.cmake/Modules Add cmake support for GUI part 2018-07-28 12:05:13 +03:00
extensions fix memory leaks 2018-08-22 13:22:37 -04:00
GUI reorganize, everything 2018-08-23 11:53:23 -04:00
host bugfixes 2018-08-23 13:15:24 -04:00
include reorganize, everything 2018-08-23 11:53:23 -04:00
vnrhook bugfixes 2018-08-23 13:15:24 -04:00
.gitattributes Line ending attributes for window LF 2016-12-12 00:50:06 +09:00
.gitignore Add cmake support for GUI part 2018-07-28 12:05:13 +03:00
CMakeLists.txt start cleaning up headers 2018-08-22 12:24:55 -04:00
CMakeSettings.json update build stuff and add the starter extensions 2018-08-19 00:13:19 -04:00
LICENSE add license and update readme 2018-05-20 21:21:37 -04:00
README.md Update README.md 2018-08-18 15:11:51 -04:00

README.md

NextHooker

Overview

NextHooker is an open-source x86/x64 text hooker for Windows.

Basically, GUI text hooker based on Stomp's ITHVNR.

Downloads

Releases of NextHooker can be found here

Previous releases of ITHVNR can be found here.

Features

  • Open-source
  • x64 supported (x64 version only works with x64 programs)
  • Hook text using /H "hook" codes (most AGTH codes supported)
  • Directly read text using /R "read" codes (Guide)
  • Auto hook many engines (including some not supported by VNR!)
  • Extensions

Extensions

See my Example Extension project to see how to build an extension.

Compiling

Before compiling NextHooker, you should get Visual Studio with CMake and ATL support, as well as Qt version 5.11
You should then be able to simply open the folder in Visual Studio, and build. Run Build/NextHooker.exe

Project Architecture

The GUI links to vnrhost.dll (created from the host folder) which injects vnrhook.dll (created from the vnrhook folder) into the target process and connects to it via 2 pipe files.
vnrhost writes to hostPipe, vnrhook writes to hookPipe (duh?)
vnrhook waits for the pipe to be connected, then injects a few instructions into any text outputting functions (e.g. TextOut, GetGlyphOutline) that cause their input to be sent through the pipe.
Additional information about hooks is shared through a file view (a.k.a. section object) that is mapped to a reference to the Hook class.
The text that vnrhost receives through the pipe is then processed a little before being dispatched back to the GUI and displayed.

Contributing

All contributions are appreciated! Please email (no, I'm not busy!) me at akashmozumdar@gmail.com if you have any questions about the codebase; I know it's messy and undercommented.
You should use the standard process of making a pull request (fork, branch, commit changes, make PR from your branch to my master).

License

GPL v3

Developers

Special Thanks

  • Everybody adding issues!