[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-83853":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":14,"stars30d":14,"stars90d":14,"forks30d":14,"starsTrendScore":14,"compositeScore":15,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":16,"fork":16,"defaultBranch":17,"hasWiki":18,"hasPages":16,"topics":19,"createdAt":9,"pushedAt":9,"updatedAt":20,"readmeContent":21,"aiSummary":9,"trendingCount":14,"starSnapshotCount":14,"syncStatus":22,"lastSyncTime":23,"discoverSource":24},83853,"rustyvnc","nzyuko\u002Frustyvnc","nzyuko","Standalone HVNC red team tool with a Rust Windows client and Go relay\u002Fviewer server.",null,"Rust",52,1,54,0,37.9,false,"main",true,[],"2026-06-12 04:01:42","# RustyVNC\n\nRustyVNC is a standalone HVNC red team tool with a Rust Windows client and a Go relay\u002Fviewer server.\n\nThe client is Rust and owns the Windows desktop, capture, JPEG encoding, application launch, and input dispatch logic. The server is Go and owns HTTPS\u002FWSS transport, frame validation, viewer fan-out, and the minimal browser UI.\n\n## Layout\n\n```text\nclient\u002F   Rust Windows client.\nserver\u002F   Go relay and browser viewer for the Linux operator host.\ndocs\u002F     Wire protocol notes.\n```\n\n## Quick Start\n\nStart the server on the operator host:\n\n```sh\ncd server\ngo run . -addr 127.0.0.1:7070\n```\n\nThe server is HTTPS-only. If `-cert` and `-key` are not supplied, it generates an ephemeral self-signed certificate for the current run.\n\nOpen the viewer:\n\n```text\nhttps:\u002F\u002F127.0.0.1:7070\u002F\n```\n\nBuild the Windows client from Linux with the MinGW target:\n\n```sh\ncd client\ncargo build --release --target x86_64-pc-windows-gnu\n```\n\nRun the client from a logged-on Windows desktop session:\n\n```powershell\nrustyvnc-client.exe --server https:\u002F\u002FSERVER_IP:7070 --debug\n```\n\nWith the generated self-signed certificate, add `--accept-invalid-certs` or install a trusted certificate and run the server with `-cert` and `-key`.\n\nThe client must run in an interactive user session. Session 0 is rejected because it produces misleading black-frame behavior rather than a real desktop capture.\n\n## How It Works\n\nThe Windows client takes an `https:\u002F\u002F` server URL and tries to open a secure WebSocket connection first. If that path is not available, it automatically falls back to HTTPS polling. Both paths stay encrypted; cleartext URLs are rejected.\n\nThe browser viewer is served from the same Go server. When the operator opens the HTTPS page, the viewer connects back over WSS and receives frames from the Windows client.\n\nThe client sends JPEG desktop frames to the server. The viewer sends mouse, keyboard, and launch actions back through the server to the client. Wire-format details live in `docs\u002Fprotocol.md`.\n\n## Notes\n\nOnly one client is supported in the first standalone server. This keeps the extraction small and makes the session lifecycle obvious. Multi-client routing can be added after the core client\u002Fserver behavior is stable.\n\nBind the server to `127.0.0.1` by default. If you bind to a non-local interface, provide a trusted TLS certificate, use the optional `-token` flag, and keep it inside an isolated network.\n\n*Footnote: RustyVNC is intended for authorized research and defense analyst purposes.*\n",2,"2026-06-11 04:11:38","CREATED_QUERY"]