build(deps): bump github.com/fatedier/frp from 0.68.1 to 0.70.1 in /airavata-agent

[dependabot]

Bumps github.com/fatedier/frp from 0.68.1 to 0.70.1.

Release notes

Sourced from github.com/fatedier/frp's releases.

v0.70.1

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

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

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

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.

... (truncated)

Commits

• fa3bcca Merge pull request #5444 from fatedier/dev
• 18eef83 fix(client): synchronize graceful shutdown duration (#5442)
• 466a94f update quic-go dependency to v0.60.0 (#5443)
• 898bcf7 web: restore Vite client declarations for both dashboards (#5415)
• 0e53833 refactor: use standard library HKDF (#5440)
• c23934b web: update vulnerable transitive dependencies (#5441)
• 23512f5 fix: upgrade go-oidc to v3.18.0 (#5439)
• 84b907a deps: bump golib to v0.8.1 (#5437)
• f8fc3c6 server: drop HTTP/1.1 h2c upgrade handling (#5436)
• 7dc7be9 ssh: fix malformed exec payload panic (#5428)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.