How doge-1satellite/ttt2 works
Project type and purpose
• This is a classic “remote administration” system consisting of:
• A Windows‐based Client GUI application (“Client/…”)
• A multi‐threaded Server daemon (“Server/…”)
• Installer modules (“Install/…”)
• Plugin subsystems (Video capture, ShellCode loader, etc.)
• Low‐level kernel drivers for extended privileges (“Server/driver/…”).
• The README is minimal, but the presence of Client/Server code, IOCP, Socket layers, shell‐code loaders and drivers shows it’s a remote control tool.
File structure
• Top‐level components:
• Bin/: final packaged executables, skins, plugin HTML scripts
• Client/: GUI front‐end (MFC dialogs, views, resource files)
• Server/: headless service, common libraries, driver source
• Install/: installer project that deploys the server component
• PluginVideo/, ShellCode/, Plugin shells: separate dynamic modules
• common/, Dllcomment/, libcef/: shared code (zlib, cJSON, video codecs)
• Build artifacts in each project’s Debug/Release subfolders.
• Kernel drivers under Server/driver/x32 and x64.
• HTML/JS assets under Bin/Plugins/*.html and Client/res/Html/.
README for additional insights
• Dependencies (zlib, xvid, cJSON, MSXML) appear in multiple common folders.