ospab c0124a19be feat(outbound): SOCKS5 username/password auth for the upstream proxy ... Adds optional username/password to the server's outbound proxy config so an upstream SOCKS5 that requires authentication — a residential-proxy service, for instance — can be used. Both the TCP-connect and UDP-associate paths now run a shared RFC 1929 negotiation: when credentials are set the client offers method 0x02 (and 0x00), and on a 0x02 selection performs the username/password sub-negotiation; a proxy that rejects all methods reports a clear "set outbound.username/password" error instead of a bare failure. No credentials = the previous no-auth behaviour, unchanged. The two on-disk config templates (`ostp init` / `ostp setup`) now carry empty "username"/"password" in the outbound block so the fields are discoverable and ready to fill. Both fields default on deserialize, so existing configs are unaffected.		2026-08-24 15:32:20 +03:00
..
src	feat(outbound): SOCKS5 username/password auth for the upstream proxy	2026-08-24 15:32:20 +03:00
Cargo.toml	fix(server): constant-time comparison for Management API secrets	2026-07-18 17:38:09 +03:00