chore(deps): update dependency fatedier/frp to v0.71.0

[renovate]

This PR contains the following updates:

Package	Update	Change
fatedier/frp	minor	0.68.0 → 0.71.0

---

Release Notes

fatedier/frp (fatedier/frp)

v0.71.0

Compare Source

Features

• UDP packet payloads for ordinary UDP proxies and SUDP now use a dedicated binary codec when frpc and frps successfully negotiate the capability under wire protocol v2, using a more compact wire representation. Wire protocol v1 remains JSON; wire protocol v2 falls back to JSON UDPPacket when the peer does not support or did not negotiate the capability.

Fixes

• Fixed a server panic and remote denial of service caused by a client sending a negative pool_count. Negative values are now rejected before work-connection pool resources are allocated.
• Fixed frpc verify ignoring configured featureGates, which caused VirtualNet configurations to be rejected even when the feature was enabled.
• Fixed a case-insensitive validation bypass that allowed customDomains under the configured subDomainHost to be registered using mixed-case domain names.

v0.70.1

Compare Source

Fixes

• HTTP vhost servers no longer support HTTP/1.1 Upgrade: h2c requests. Cleartext HTTP/2 prior-knowledge remains supported.
• Fixed control-session replacement leaks when frpc reconnects through a half-open TCP multiplexed connection.
• Fixed an SSH tunnel gateway panic when handling malformed exec requests.

v0.70.0

Compare Source

Features

• Expanded the frps dashboard API v2 migration across Clients, Proxies, Server Overview, Client Detail, and Proxy Detail, covering paginated users/clients/proxies, detail data, proxy traffic history, server system info, offline proxy statistics pruning, server-side pagination, search, and proxy type filtering.

Fixes

• WebSocket and WSS tunnel payloads are now sent as binary frames, avoiding disconnects through RFC-compliant intermediaries that validate text frames as UTF-8.
• The tls2raw client plugin now writes the proxy protocol header to the local raw connection when proxy protocol is enabled.
• frpc now rejects duplicate proxy and visitor names in config files instead of silently overwriting earlier entries.

v0.69.1

Compare Source

Features

• transport.wireProtocol = "v2" now also applies to UDP-based proxy payloads, including ordinary UDP and SUDP, so their payload framing is consistent with the selected wire protocol.
• Improved SUDP compatibility during mixed transport.wireProtocol deployments, allowing frps to bridge payloads between v1/default and v2 SUDP clients.
• XTCP work connection NatHoleSid messages now follow the selected transport.wireProtocol.

Compatibility Notes

• When enabling transport.wireProtocol = "v2" for SUDP, upgrade both the proxy and visitor frpc instances first, or keep them on v1 until both sides are upgraded.

v0.69.0

Compare Source

Compatibility Policy

Starting with v0.69.0, each minor release is supported until there are nine newer minor releases. For example, v0.69.0 will be supported until v0.78.0 is released. Within this window, frpc v0.69.0 is guaranteed to work with any frps from v0.61.0 to v0.77.0, and vice versa. Patch releases within the same minor are always compatible. Versions outside the support window may continue to work on a best-effort basis, but compatibility is no longer guaranteed.

For mixed-version deployments, upgrade frps first, then upgrade frpc. This keeps the server side ready for newer client-side protocol behavior before clients start using it.

Notes

This release introduces wire protocol v2 as a transition path for future frpc/frps protocol changes. The existing wire protocol is difficult to extend without compatibility risk, and upcoming changes, including replacing deprecated stream encryption methods, require a versioned protocol.

The default value of transport.wireProtocol remains v1 in this release. Users can keep the default for now. To test v2 early, upgrade both frpc and frps to versions that support it, then set transport.wireProtocol = "v2" in frpc. A v2-enabled frpc cannot connect to an older frps.

When transport.wireProtocol = "v2" is enabled, the control channel uses negotiated AEAD encryption after the login handshake. Both frpc and frps must be upgraded to this release to use v2.

v1 will be deprecated when v2 becomes the default in a future release. It will continue to be supported until v0.78.0 is released, and may be removed in v0.78.0 or later.

Features

• Added transport.wireProtocol for frpc to select the internal message protocol used between frpc and frps. Supported values are v1 and v2.
• Added client protocol visibility in the frps dashboard and /api/clients API. Online clients now report their negotiated protocol as v1 or v2.
• Wire protocol v2 now negotiates AEAD control-channel encryption. Supported algorithms are xchacha20-poly1305 and aes-256-gcm; frpc advertises its preferred order based on local AES-GCM hardware support, and frps selects the first supported algorithm from that list.

v0.68.1

Compare Source

Fixes

• Fixed a configuration-dependent authentication bypass in type = "http" proxies when routeByHTTPUser is used together with httpUser / httpPassword. This affected proxy-style requests. Proxy-style authentication failures now return 407 Proxy Authentication Required.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.