MHSanaei 61b59bb868 fix(integration): cap WARP API response body size ...

doWarpRequest read the response with an unbounded io.ReadAll, unlike the
sibling NordVPN client which already caps every read at maxResponseSize.
A hostile panel egress proxy or a MITM on the Cloudflare WARP endpoint
could stream an arbitrarily large body and force the panel into an
unbounded allocation. Wrap the body in an io.LimitReader(maxResponseSize)
to match the NordVPN client.

2026-07-15 04:36:30 +02:00

..

nord.go

style: adopt golangci-lint v2 and resolve all findings

2026-06-27 15:42:22 +02:00

panel_egress_test.go

feat: replace panel proxy URL with outbound-based egress bridge

2026-06-10 23:52:20 +02:00

warp_response_test.go

fix(integration): cap WARP API response body size

2026-07-15 04:36:30 +02:00

warp.go

fix(integration): cap WARP API response body size

2026-07-15 04:36:30 +02:00