You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(dgw): route KDC traffic through agent tunnel (DGW-384)
When an agent advertises the KDC's subnet or DNS domain, route Kerberos
traffic through the QUIC tunnel just like every other proxy path. This
closes the last gap left after the transparent routing PR (#1741):
- `/jet/KdcProxy` HTTP endpoint — `send_krb_message` now consults the
routing pipeline before falling back to direct TCP. The HTTP handler
has no parent association, so it mints a fresh session_id purely for
agent-side log correlation.
- RDP CredSSP/NLA — `rdp_proxy.rs::send_network_request` previously
hard-coded `None` for the agent handle. Plumb `agent_tunnel_handle`
and `session_id` from `RdpProxy` down through `perform_credssp_with_*`
→ `resolve_*_generator` → `send_network_request`. The same change
reaches the credential-injection clean path (`rd_clean_path.rs`).
`session_id` here is `session_info.id` / `claims.jet_aid` so the
agent log ties KDC sub-traffic to its parent RDP session.
Stack: based on #1741. Picks up `agent_tunnel::routing::try_route`.
`send_krb_message` signature gains `(agent_tunnel_handle, session_id)`
in that order — required `Uuid`, no `Option<>` — so the call site is
honest about which UUID it's logging. The UDP scheme guard (KDC over
UDP keeps going direct because the agent protocol only carries TCP)
and the 64 KiB `MAX_KDC_REPLY_MESSAGE_LEN` DoS cap (and the matching
generic `read_kdc_reply_message`) come along since they live in the
same file and serve the same end.
0 commit comments