Crimson Relay 0.2.0 -- verified 2026-11-03

PASS: 16 unittest cases covering consent, pairing, authorization, one-use legacy
job results, DPAPI, public/private target rules, DNS pinning and mixed-answer
rejection, HTTP proxy authentication and header rewriting, opaque CONNECT
forwarding, no-participant response, and active revocation. Landing/download/
admin HTTP responses and strict security headers are also covered.

PASS: Python compilation; admin and download JavaScript syntax checks.
PASS: Tk UI required size 630x683 fits 680x740. Starts paused, consent unchecked,
and no forwarding worker runs at startup.
PASS: actual 0.2.0 NSIS installer installs per-user into isolated staging, with
valid Windows uninstall registry command. Frozen GUI opens/closes normally.
Embedded application and uninstaller both carry the expected test signature.
Uninstallation removes the staged application and registry entry.

PASS: real deployed public-web proxy tested first through the fallback HTTPS
path, then again through https://relay.dbcrimson.com after DNS propagated.
HTTP and HTTPS example.com both returned 200. HTTPS uses normal destination
certificate validation. api.ipify.org through the proxy returned the same
public IP as this PC's direct connection (IP not logged). Unauthenticated
proxy access returned 407. Revoking the temporary participant closed an
already established CONNECT socket. Four proxy session records and 11303
bidirectional bytes were observed in the final test. Temporary participant
revoked and SSH listener closed afterward. No global proxy settings changed.

PASS: relay.dbcrimson.com DNS A -> 148.113.250.199 and public HTTPS certificate.
Landing /, download /download/, operator /admin/, and CSS/JS assets return200.
VPS API9092 and proxy9093 listen only on127.0.0.1. Existing main site returns
200; crimson-hub, crimson-auth, crimson-relay and Caddy all remain active.

SIGNING: application, installer and embedded uninstaller signed with
CN=Crimson Relay Local Network Test (90-day self-signed code-signing cert).
Private key nonexportable in CurrentUser/My. Public certificate supplied.
No root/publisher trust store modified. SignTool's production /pa verification
reports untrusted root; these are LOCAL TEST signatures, not publicly trusted
production publisher signatures. No external timestamp is attached.

LIMIT: automatic approval review rejected the headless Chrome preview launch
with reason 'blocked by policy'. Browser visual/interaction QA is therefore
unverified. HTTP, transport, package, signature-presence and checksum checks
were completed instead. No certificate or browser security bypass was used.

NOT COMPLETED: publicly trusted publisher signing, independent security audit,
broad Windows compatibility, load testing, payment/billing, commercial rollout,
automated retention/deletion and production customer onboarding.
