The POSIX clients were built without a connection config - Linux, macOS and Android all construct IOCPClient without the injected CONNECT_ADDRESS - so ConnectServer saw protoType -1 and quietly dialled the master port in plain TCP. Setting protoType to WS in their settings did nothing and logged nothing, and since CLIENT_CAP_PROTO_SWITCH is Windows-only the server could not move them either. Give the client a SetDefaultProto() for that construction path and call it from all three mains before the reconnect loop, with a one-shot log when neither a conn nor a default protocol is available so the silent fallback becomes visible next time. Bound what a peer can make the client read. ReadHeader accepted the 8-byte extended length and rejected only the sign bit, so a frame length of nearly 2^63 kept the connection streaming into a frame that would never end - alive but never delivering another packet. Cap single frames at 256 MB, the same value ServerWsSession already applies to client frames, and drop the connection past it; real traffic is far below that. Stop Reset() from writing the receive thread's frame state. Disconnect() can run from the heartbeat or command thread, not just the receive thread, so Reset() now only flips the atomic ready flag and a new ResetFrames() clears m_remaining, m_masked and m_maskPos from Handshake() alone, before the receive thread starts reading the socket. Those fields keep a single owner without adding a lock to the receive hot path. Finish a dead WS session instead of leaving it to the keepalive timer. When the session had closed but wsState was still WS_Ready, sends were dropped and nothing woke the pending recv, so a peer that closed and then went quiet held the context for the 3-minute keepalive. shutdown() the socket there so the recv returns zero bytes and the normal -2 teardown runs; RemoveStaleContext would deadlock against the caller's own IoRefCount and can hand back a reused context. That shutdown only finishes the connection if a zero-byte read still tears it down, and on the plain path it no longer did. DispatchPlain answers an empty buffer with "handled", so a peer's FIN left the connection in CLOSE_WAIT until keepalive - holding an IOCP context, a pending WSARecv and a rate-limit slot - where the pre-WS code called ParseReceivedData and tore down at once. Restore that teardown on the TLS_Plain branch, matching the other two. Checked against a Debug server: a plain socket that half-closes used to sit in CLOSE_WAIT with the peer's recv timing out, and now disappears immediately with recv returning zero. Two smaller cleanups from the same review. Give the WS upgrade its own prefix buffer (wsPreClassify) instead of borrowing the TLS sniffer's, which was serially reused for two state machines and read as if it were one. And stop deriving the build dialog's protoType from the combo box index: items now carry the protocol value as item data, keyed off the index AddString returns, so inserting an option in the middle can no longer write the wrong number into the generated client without any error. ApplyProtoSwitch loses its bool return, which contradicted its own side effects and was ignored by every caller. Co-Authored-By: deepseek-flash
macOS Remote Desktop Client =========================== Prerequisites: 1. Xcode Command Line Tools: xcode-select --install 2. CMake: brew install cmake Build: chmod +x build.sh ./build.sh Or manually: mkdir build && cd build cmake .. make Run: ./build/bin/ghost Configuration: Server address is configured in main.mm (g_SETTINGS variable). Modify before building if needed. Permissions Required: 1. Screen Recording - System Settings > Privacy & Security > Screen Recording 2. Accessibility - System Settings > Privacy & Security > Accessibility Features: [x] Screen capture (CGDisplayCreateImage) [x] H264 video encoding (VideoToolbox) [x] Mouse control (move, click, drag, scroll) [x] Keyboard control (full VK code mapping) [x] Retina display support (coordinate scaling) [x] Network connection (IOCPClient) [x] LOGIN_INFOR (system info reporting) [x] Heartbeat with RTT estimation [x] Active window tracking [x] Quality level adjustment (FPS/algorithm) Files: CMakeLists.txt - Build configuration Permissions.h/mm - macOS permission handling ScreenHandler.h/mm - Screen capture and H264 encoding InputHandler.h/mm - Mouse/keyboard simulation H264Encoder.h/mm - VideoToolbox H264 encoder SystemManager.h/mm - Process management main.mm - Entry point, LOGIN_INFOR, heartbeat Quality Levels: Level 0: 5 FPS, Grayscale (emergency low bandwidth) Level 1: 10 FPS, RGB565 Level 2: 15 FPS, H264 (default, office work) Level 3: 20 FPS, H264 Level 4: 25 FPS, H264 Level 5: 30 FPS, H264 (smooth) Notes: - First frame is always raw bitmap (TOKEN_FIRSTSCREEN) - Subsequent frames use H264 encoding (TOKEN_NEXTSCREEN) - Coordinates are scaled for Retina displays automatically - Windows VK codes are mapped to macOS key codes