Feature: run a test client inside the master from the Advanced menu

The Advanced menu now ends with Run Test Program. It copies the kernel
payload that was already read into memory, points its CONNECT_ADDRESS at
127.0.0.1:<listen port>, and loads it with MemoryLoadLibrary inside the
master process, so this machine comes online as a controlled host -- no
second machine is needed to try remote desktop or file transfer. A
worker thread waits for the client to exit, then frees the module and
re-enables the item. Only one instance runs at a time: the item is
grayed while it does, and stopping it means uninstalling the test host
from the online list.

The loaded copy carries LOCAL_TEST_CLIENT_MAGIC in szFuture. The client
uses that mark to refuse the commands that would otherwise hit the host
process or the whole machine: uninstall (no self_del), update, run as
admin, ban, share/assign, and shutdown/reboot/logoff. It also skips
auth-kernel detection, which GetModuleFileName(NULL) would misjudge
inside the master.

Renames szFututre to szFuture and documents that the first 16 bytes of
the reserved tail are now claimed, with a static_assert so it cannot
silently shrink below the magic.

Translations for en_US, zh_TW and de_DE, plus the HIDE_MENU_RUN_TEST
feature flag and its row in the limits dialog.

Verified on a Debug master: the item is last and has its icon, one click
brings the host online, a second click is refused, uninstall stops it in
about a second and the master survives, re-run works, and exiting the
master with a live test client takes 2.6s (3.0s baseline).

Co-Authored-By: deepseek-flash
This commit is contained in:
yuanyuanxianganddeepseek-flash committed 2026-11-06 17:17:18 +01:00
1 parent cc9ce35c4d
commit f77b18aa68
18 files changed
+268 -11

No files matched your search

+4 -1
View File
@@ -791,7 +791,10 @@ DWORD WINAPI StartClient(LPVOID lParam)
}
}
std::string expiredDate;
BOOL isAuthKernel = IsAuthKernel(expiredDate);
// 主控端「运行测试程序」加载的实例跑在主控进程里:GetModuleFileName(NULL) 是主控 EXE,
// 而主控 EXE 一定大于 16MB,「YAMA_<pid>/EVENT_<pid>」事件也可能是上一轮测试残留,
// 会被 IsAuthKernel 误判成授权内核并改写连接地址。测试实例一律按普通客户端跑。
BOOL isAuthKernel = IsLocalTestClient(&settings) ? FALSE : IsAuthKernel(expiredDate);
if (isAuthKernel) ParseAuthServer(&settings);
// 内嵌 TLS 信任锚只在「连的正是生成时那台主控」时生效(见设计文档 §3.6)。这个判定