40 lines
4.0 KiB
Markdown
40 lines
4.0 KiB
Markdown
# Verification record
|
|
|
|
Validated on Windows x64 during implementation:
|
|
|
|
- `go test ./...`: role authentication, offline devices, duplicate registration, exclusive leases, ticket ownership and replay rejection, bidirectional bytes, stream cancellation, agent disconnect cleanup.
|
|
- `go vet ./...`: passed.
|
|
- `cargo test --workspace --locked`: configuration validation and ADB smart socket handshake with fragmented replies.
|
|
- `cargo clippy --workspace --all-targets --locked -- -D warnings`: passed.
|
|
- Release builds: Go relay and both Rust executables built successfully.
|
|
- `python tests/e2e.py` against the release binaries: passed 2 MiB binary transfer, eight concurrent streams, an idle stream across control ping/pong, competing-client rejection, agent restart and relay restart recovery.
|
|
- Existing Python bridge unit tests: all three passed.
|
|
|
|
Read-only real-device smoke test:
|
|
|
|
- Remote ADB Server `192.168.5.222:5037` listed `192.168.100.141:5555` as online.
|
|
- Started a temporary relay and both Rust daemons, with the gateway using the existing remote ADB transport.
|
|
- Initial attempt reached the phone but returned `unauthorized`. After the user approved the local computer's key, the same test was rerun successfully.
|
|
- Ordinary local `adb devices -l` listed `127.0.0.1:51847` as `device`, with product `aosp_crosshatch` and model `AOSP_on_crosshatch`.
|
|
- Remote `adb shell getprop ro.product.model` returned `AOSP on crosshatch`; the read-only shell echo marker also matched. All three release programs were involved in the successful test.
|
|
- App installation, Android Studio and scrcpy have not yet been exercised through the new path.
|
|
- Temporary processes and local ADB endpoint were disconnected after the test; unrelated local ADB devices were preserved.
|
|
|
|
Public deployment follow-up:
|
|
|
|
- Linux amd64 server is now running on Debian 12 at `175.178.213.60`, as an enabled systemd service under a dedicated user.
|
|
- Existing Nginx proxies `https://ttstd.com/ads/` to loopback `127.0.0.1:18081`, stripping the prefix. Its existing root-domain certificate was verified without disabling certificate checks.
|
|
- A real public WSS smoke test passed: both Rust daemons connected to the public origin while keeping TLS SNI/hostname `ttstd.com`; ordinary local ADB listed `127.0.0.1:59671` as `device`, and both read-only shell commands passed.
|
|
- The initial public test used a temporary local gateway and the VPN-reachable remote ADB Server. Follow-up deployment now runs the actual gateway on the remote Windows PC; see the next section.
|
|
- Public Cloudflare DNS connectivity timed out from the current PC; the explicit origin-address option was used. No DNS records were changed.
|
|
- macOS runtime and Linux Rust daemon hosting remain untested. See `deployment-ttstd.md` for deployed configuration and certificate expiry.
|
|
|
|
Remote Windows gateway follow-up:
|
|
|
|
- Installed release `ads-agent.exe` on `192.168.5.222`, under `C:\Users\TT\AppData\Local\AndroidDeviceStreaming\agent`. Remote SHA256 matched the local release artifact.
|
|
- Created an ACL-protected credential directory and registered `ADS-Agent` as a hidden background task under `TT`, with password logon, startup/logon triggers and failure restart. No account password is written into source or deployment files.
|
|
- The gateway directly connects to phone `192.168.100.141:5555` and public relay origin `175.178.213.60:443`, retaining hostname `ttstd.com` and normal TLS checks.
|
|
- Ran `tests/real_device.py --existing-device home-phone`: only a local client was started; no local gateway and no remote ADB Server transport were used. Ordinary local ADB showed the phone as `device`, and model query plus shell marker passed.
|
|
- Restarted the remote task and repeated that test: passed again, with local endpoint `127.0.0.1:49832` and model `AOSP on crosshatch`.
|
|
- Remote gateway remains running. Temporary local smoke-test endpoints/processes were cleaned up. Startup trigger configuration was inspected without rebooting the PC. System VPN was not disabled; it was only needed for remote SSH management, not the tested ADB data path.
|