Kelsi
|
f032ae8455
|
Integrate Unicorn emulator into WardenModule
Connected cross-platform emulation to module execution pipeline!
Integration Points:
- Added emulator_ member to WardenModule
- Initialize emulator in initializeModule() when HAVE_UNICORN defined
- Setup Windows API hooks automatically
- Ready to call module entry point via emulated execution
Changes:
- WardenModule now has moduleBase_ (0x400000 default)
- Emulator initialized with loaded module code
- Common Windows APIs hooked (VirtualAlloc, GetTickCount, etc.)
- processCheckRequest() prepared for emulated execution
Build Flow:
#ifdef HAVE_UNICORN
→ Use Unicorn emulator (Linux/macOS/ARM)
#elif _WIN32
→ Native Windows execution
#else
→ Platform not supported
#endif
Status:
✅ Emulator infrastructure integrated
✅ Module code loaded into emulated environment
✅ API hooks ready
⏳ Entry point calling (TODO - needs callback struct setup)
⏳ PacketHandler execution (TODO - needs implementation)
Next: Call module entry point with ClientCallbacks structure
|
2026-02-12 03:04:08 -08:00 |
|
Kelsi
|
4b425f1225
|
Implement Warden module execution foundation (Phase 1 & 2)
Added architecture for loading and executing native x86 Warden modules:
New classes:
- WardenModule: Individual module loader with 8-step pipeline
✅ MD5 verification (working)
✅ RC4 decryption (working)
⏳ RSA/zlib/exe-parsing/relocation/API-binding/execution (TODOs)
- WardenModuleManager: Module lifecycle and disk caching
~/.local/share/wowee/warden_cache/<MD5>.wdn
- WardenFuncList: Callback structure for module execution
Integration:
- Added wardenModuleManager_ to GameHandler
- Module manager initialized on startup
- Foundation ready for phases 3-7 (validation → execution)
Documentation:
- WARDEN_MODULE_ARCHITECTURE.md (comprehensive 7-phase roadmap)
- Estimated 2-3 months for full native code execution
- Alternative: packet capture approach (1-2 weeks)
Status: Crypto layer complete, execution layer TODO
|
2026-02-12 02:43:20 -08:00 |
|