Compare commits

..

7 Commits

Author SHA1 Message Date
Alberto Xosé Méndez Taboada
e8eead5715 Add Galician language support for UI strings (#16101) 2026-09-07 13:31:19 +08:00
cui fliter
92d787b885 fix: clipboard, preserve uncompressed special format data (#16100)
Signed-off-by: cuishuang <imcusg@gmail.com>
2026-09-07 11:12:52 +08:00
rustdesk
692113c87e bump webrtc: probe on T3-rtx, settle the rest by the SACK, RTO from the latest send
Sending without a congestion window, a T3-rtx resent everything in flight, and
on a 5 Mbps link with 300-500ms stalls that spiralled: seconds of latency and
several times the bytes. The fork now resends everything outstanding on a
timeout only when it packs into four packets; otherwise it resends one packet
and withholds the rest until the SACKs settle them (RFC 4960 6.3.3 E3, F-RTO):
an original acked takes the marks off, a first transmission made after the
timeout acked with the rest still missing sends them, and with nothing else to
tell, a probe acked no sooner than the least RTT after it went out draws the
next probe, two of them settling the rest as lost. A restarted RTO is counted
from the latest send as QUIC does, backs off from the full RTO, and floors at
KCP's 30ms with srtt + 25ms at the least. Lost tails of up to four packets and
sparse small messages under loss now recover at KCP's pace where they trailed
it by a frame; a stall no longer resends the backlog behind itself.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns
2026-09-06 14:46:52 +08:00
bovirus
dc04b911a1 Update it.rs (#16085)
* Update it.rs

* Update it.rs

---------

Co-authored-by: RustDesk <71636191+rustdesk@users.noreply.github.com>
2026-09-06 11:29:17 +08:00
rustdesk
254d98129d ci: use thin LTO for the armv7 sciter build
The nightly armv7 sciter build aborts while compiling the final `rustdesk`
binary:

    fatal runtime error: Rust cannot catch foreign exceptions
    error: could not compile `rustdesk` (bin "rustdesk")  (signal: 6, SIGABRT)

armv7 is the only 32-bit target in this job that links the whole binary, and
`[profile.release]` uses fat LTO with codegen-units = 1, so LLVM merges every
module into a single unit and runs past the ~3GB address space a 32-bit
process gets. The allocation failure surfaces as a C++ bad_alloc unwinding
into rustc's Rust frames, which is what that "foreign exceptions" abort is.
The x86_64 sciter build uses the same settings and passes, as do aarch64 and
every other 64-bit job in the same run, so this is specific to the 32-bit
address space rather than to the source change itself.

It started failing once the crate graph grew (hbb_common is pulled with the
`webrtc` feature unconditionally), which pushed an already marginal target
over the limit.

Use thin LTO with more codegen units for armv7 only. Peak memory stays
bounded while cross-crate inlining is kept, and 64-bit targets are untouched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Lq6xFoeEmjcuKwRx1GfdQ2
2026-09-06 10:52:37 +08:00
rustdesk
942810d432 bump hbb_common: main after the webrtc merge
rustdesk/hbb_common 3d6fb2c, the merge of PR #579; the tree is the one
470612b already pointed at, now reachable from main.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns
2026-09-06 00:24:04 +08:00
RustDesk
ae6af2de43 Webrtc (#15684)
* feat: add rendezvous WebRTC signaling fields

* feat: route WebRTC ICE on controlled side

* feat: race WebRTC as a direct transport enhancement

* fix: route WebRTC ICE through rendezvous paths

* feat: WebRTC transport racing, DTLS identity binding, and pc-leak fixes

- prefer-P2P racing (race_transports_prefer_webrtc) across punch and RelayResponse; ICE bridge with 400ms candidate resend
- controlled-side answerer and ICE routing; sign local DTLS fingerprint into SignedId, controller verifies the binding fail-closed
- fix pc leaks: close_webrtc() on insecure-decline paths (io_loop, port_forward); compute direct before disarming the offerer guard
- point hbb_common to the WebRTC data-plane commit 9f5a296

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* fix: preserve WebRTC transport preference

* feat: decouple WebRTC from UDP punch, route controlled signaling over TCP

- the WebRTC offer now rides any punch request; only an offer-less request
  may close and reuse the rendezvous socket for TCP punching
  (request_allows_tcp_punch replaces the udp_port-based invariant), with a
  separate offer-less request racing as the TCP fallback
- WebSocket mode no longer disables WebRTC — ws only tunnels the
  signaling/relay legs while ICE stays the only P2P path there; SOCKS proxy
  still disables it (ICE would bypass the proxy and leak the real IP)
- controlled side: WebRTC-only punch replies and trickled ICE candidates go
  over dedicated TCP connections to the rendezvous server instead of the UDP
  mediator channel, for ws/TCP-only hbbs deployments; drop the now-redundant
  rz_sender plumbing and the 400ms candidate re-send on that leg
- guard is_udp handling against responses to requests that advertised no
  udp_port; skip the IPv6 socket bind under force-relay
- test_udp_uat: drop the STUN port race — the punch port must come from the
  rendezvous server's TestNatResponse observing this socket's mapping, a
  STUN probe from another socket can advertise an unreachable port
- bump hbb_common (webrtc 0.13 MSRV pin rationale + upgrade checklist docs)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: KCP/UDP resilience to ICMP resets; optional KCP congestion control

- treat ICMP-driven UDP socket errors (WSAECONNRESET 10054 on Windows,
  ECONNREFUSED on Linux) as packet loss in punch_udp and the KCP pump
  instead of tearing the session down; KCP retransmits through them and a
  truly dead link is still reaped by the pong/app-level timeouts
- resolve STUN hostnames via tokio::net::lookup_host so DNS never blocks a
  runtime worker; fix the inverted non-IPv4 error message
- add enable-kcp-congestion-control option (default on): switch the turbo
  profile to nc=0 so brief loss on constrained links no longer spirals into
  stalls; sender-side only, no wire negotiation
- pin kcp-sys to the rustdesk-patches branch: upstream main lost the
  RustDesk patches on the EasyTier sync, and this branch also wires
  set_kcp_config_factory into connection setup, making the option effective

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: carry switch_code through WebRTC relay fallbacks after rebase

The rebase onto master (switch-code feature) added an 8th request_relay
parameter; pass the interface's switch code from both WebRTC->relay
fallback paths so a role-swap session survives the fallback. Also drop
a duplicate bindgen 0.72.1 entry the Cargo.lock merge produced.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: don't let the preferred branch's own relay preempt a direct fallback

race_transports_prefer_webrtc committed any success from its first argument
outright, on the assumption that it is the WebRTC connect. It is not: the call
site passes a whole punch attempt, which internally falls back to request_relay
when its direct transports fail. That relay was therefore committed instantly
while the offer-less fallback's TCP punch was still in flight — inverting the
preference this function exists to enforce, since the is_p2p predicate the
caller already supplies was applied only to the `others` branch.

Apply it to both branches: a direct result from either side still commits
immediately, and a relayed result from either side is held for the window so
the other side can land something direct. Also commit a held connection when
the surviving branch errors, which the previous code only did on the first
branch's failure path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: evict the oldest pending ICE candidate, not the newest

Candidates arrive in gathering order — host, then srflx, then relay — so a
full buffer was discarding exactly the ones that traverse NAT while keeping
host ones that only work on a shared LAN. Evict from the front instead.

Also document why the controller's ICE bridge must not reconnect on error, in
contrast to the controlled side's per-candidate retry: its socket address is
the return route itself (mangled into PunchHole.socket_addr, echoed back in
IceCandidate.socket_addr, resolved through tcp_punch), so a reconnect would
arrive from an address no route points at, and the server drops the old entry
when the connection closes. Once it dies both directions are dead, and
abandoning WebRTC is the correct response rather than retrying.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: bound log volume on sites whose rate a peer or retry loop controls

Debug output goes to the log file, so a site that fires per received message
or per retry lets someone else decide how much a machine writes to disk. The
WebRTC work added the first such sites.

- KCP io loop: absorbing ICMP errors as packet loss made a broken socket write
  ~100 lines a second for the 60s until the pong timeout reaps it. Log by run
  instead: one line when a run starts, one per ~5s while it persists so a stuck
  socket stays visible, and one on recovery with the total.
- punch_udp: the recv error retries every 10ms for up to MAX_TIME, so one line
  per occurrence wrote thousands per punch. Log the first, report the count in
  the timeout message.
- ICE candidate paths (client, mediator): the peer sets the candidate rate and
  the rendezvous route carrying them needs no prior punch, so throttle to one
  line a minute each with the suppressed count.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: the KCP io throttle reset itself every cycle, so it never throttled

The send and recv arms shared one counter, and an ICMP error on a connected
socket is reported once and then cleared — so the steady state is an
alternation: the send succeeds and clears the counter, the next recv reports
the error and finds the counter at 1, and logs. Every error still wrote a
line, at the ~100/s the previous commit set out to stop, while the
persistent-failure and recovery branches were unreachable.

Use one LogThrottle per direction instead of a hand-rolled counter. That
removes the shared state the bug lived in, drops a third throttling mechanism
in favour of the one already added, and leaves the surrounding `if let Err`
untouched rather than reshaping it into a match.

Also fix test_udp_uat's socket-error arm, the untreated twin of the punch_udp
site: it had no backoff at all, so a persistent error re-armed recv
immediately and spun the loop at CPU speed, one warn line per iteration.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump kcp-sys: 14 review fixes on rustdesk-patches (6e44b93 -> fa51c15)

Picks up the handshake-recovery work plus the review round on top of it:
ABBA deadlock between the endpoint's two DashMaps, graceful-close tail
truncation, mid-stream hole on ikcp_send failure, FIN retransmission for
lost-FIN half-open hangs, SYN-ACK budget burned on dropped packets,
spurious ConnectTimeout after a completed handshake, accept-backlog
overflow stranding conns, aliasing UB in the output callback, and the
log-facade/throttling cleanup (per-packet sites no longer reach the
debug-level file logger, peer-rate warns throttled).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* ws: decouple ICE policy from force_relay — full-ICE WebRTC over WebSocket

WebSocket support folds into force_relay because a ws tunnel kills
classic TCP/UDP punching — but that conflated transport necessity with
relay policy, and the WebRTC decisions keyed off the merged flag: a ws
client built no offerer at all without TURN, and only a Relay-only-ICE
one with it. ws deployments could never reach a direct WebRTC
connection, which is exactly the path they are supposed to live on.

Split the flag. LoginConfigHandler now tracks policy_relay (the
force-always-relay option, an explicit relay request — /r ids and
retry-via-relay included — and proxy) separately; force_relay stays
policy_relay || use_ws() and keeps governing the classic paths, so
non-ws behavior is unchanged everywhere:

- the offerer's existence and ICE policy follow policy_relay: under
  pure ws the offer gathers every candidate type and may go direct;
  under relay-by-policy it stays Relay-only ICE, TURN-gated, exactly
  as before;
- the RelayResponse race applies the prefer-P2P window under ws (a
  direct ICE path is worth delaying an already-ready relay for) while
  policy relay keeps first-success semantics;
- the request carries webrtc_all_ice (hbb_common 64b54ab) so the
  controlled side knows the offer is full-ICE: it answers with full ICE
  and no TURN requirement, while offers without the bit keep today's
  relay-only answer path on every version-skew combination.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump kcp-sys: 7 review fixes on rustdesk-patches (fa51c15 -> 023a006)

Reverts the connect/accept/add_conn changes that regressed concurrent
connects (the state_map guard held across add_conn is load-bearing), states
the single-conn contract on KcpEndpoint so shared-endpoint behaviour stops
consuming review effort, pins the two invariants that keep truncated input
from aborting under panic='abort', and fixes three findings from external
review: sendwnd() echoing raw config instead of KCP's effective window (a
non-positive factory value stalled sending forever), the passive closer's
lost final FIN delaying EOF by up to ~20s, and the doubled window
overflowing for extreme factory values.

Lock-only change: cargo update -p kcp-sys also re-picked libloading's
windows-targets between two versions already present in the lock; that was
reverted to keep this commit to the one line it is about. cargo metadata
--locked passes on the result.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* ws: read the all-ICE declaration from the offer envelope, drop the proto field

Companion to hbb_common 68d2729: the full-ICE declaration now lives as
an `ice_policy: "all"` key inside the webrtc:// envelope, so the request
assembly no longer sets webrtc_all_ice and the controlled side asks the
envelope (endpoint_declares_all_ice) instead of a PunchHole field. The
rendezvous server carries the offer opaquely — no forwarding to keep in
sync. Skew behavior is unchanged: an unmarked or unparseable envelope
reads as the old Relay-only semantics.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* add enable-webrtc option; gate test_ipv6 under forced relay

OPTION_ENABLE_WEBRTC (hbb_common 48c2d4d) follows the udp/ipv6 punch
options end to end: default on against the public server, off against
private ones, same settings UI placement on desktop and mobile, and the
same bool2option local-option handling. Gates:

- controller: should_create_webrtc_offerer checks it first — no pc, no
  STUN/TURN gathering, no offer in the request;
- controlled: unlike the udp/ipv6 legs, which deliberately follow the
  request, answering builds a pc that gathers ICE from this host, so
  the answerer honors this machine's own switch too.

Translations for "Enable WebRTC P2P connection" added to all 50 lang
files next to the IPv6 entry (IPv6 and WebRTC are invariant terms in
the same grammatical slot in every one of them).

Also stop probing v6 reachability (test_ipv6) under any forced relay:
the v6 punch socket is never bound there, so the probe was wasted work
on every ws/proxy/relay connection.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* kcp: client-side integration tests over real loopback sockets

kcp-sys has been through two review rounds of behavioral fixes; the
client wrapper (kcp_io pumps, connect/accept deadlines, framed-stream
adaptation, guard lifetimes) had no tests pinning what rustdesk actually
relies on. Four now do, each through real 127.0.0.1 UDP sockets and the
BytesCodec framing sessions use:

- handshake + bidirectional framed roundtrip + graceful close: the peer
  observes end-of-stream instead of hanging (guard outlives the framed
  stream so the FIN goes out);
- a writer that queues 50 frames and closes immediately loses none of
  them - the client-side pin for the close-tail-drain semantics;
- socket errors after the peer vanishes are treated as loss: writes keep
  succeeding, nothing tears down (ICMP is advisory on connected UDP);
- the connect deadline holds when nothing answers.

Mutation-checked: dropping inbound forwarding in kcp_io reddens exactly
the three tests that need the pump, and the timeout test alone stays
green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* ipc/auth: replace the local throttle with the shared throttled_log!

auth.rs predated hbb_common's LogThrottle and grew its own equivalent:
same shape (last_log_at + suppressed), same 5s interval, plus a helper
and three OnceLock<Mutex<..>> statics. It also counted the other way -
excluding the event being reported - so each of the three sites carried
two near-identical log::warn! arms to avoid printing "suppressed 0".

The shared macro covers all of it: one static per call site declared by
the expansion, and the multiplicity suffix appears only when there is
one, which is what those duplicated arms were for. 102 lines out, 27 in.

Behavior difference, deliberate: a burst now reads "(x47)" - the total
including this line - instead of "(suppressed 46 similar events)". One
number, no arithmetic, and one convention across the codebase.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* kcp: make the congestion-control profile opt-in, not the default

The branch had flipped KCP to nc=0 (built-in congestion window) for
every session. That is a transport-behavior change for all users made on
reasoning alone, and the reasoning does not decide it: which profile wins
depends on why packets are being lost.

nc=1 - what RustDesk has always shipped - never shrinks the send window,
so on a genuinely congested uplink it deepens the loss it is reacting to.
But nc=0's backoff is blunt: a fast retransmit halves the window while an
RTO sets cwnd = 1 outright (ikcp.c) and recovery slow-starts from one
packet, so on a link with random loss and no congestion - Wi-Fi
interference, a long-haul path - it reads loss as congestion and can
stall an interactive stream for seconds. That failure mode is also the
more visible one to a remote-desktop user.

No benchmark settles this either: a loopback A/B has no bottleneck queue,
hence no congestion to control, and would flatter nc=1 by construction.
Deciding it needs a shaped link or field data.

So keep the profile users already run and let the other one be asked for
("enable-kcp-congestion-control" = "Y"). Flipping the default later is a
one-line change once there is evidence. kcp-sys keeps its own test
covering the nc=0 path.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* android: define getifaddrs/freeifaddrs for the api-21 sysroot

Turning on hbb_common's "webrtc" feature pulls webrtc-util into the android
link, and its ifaces() -- reached from vnet::Net::new() on every ICE gather --
calls getifaddrs(). bionic exports getifaddrs/freeifaddrs only from API 24,
while flutter/ndk_*.sh builds against --platform 21, so every abi failed to
link on the undefined symbols.

Raising the platform to 24 would have to drag minSdkVersion 22 with it and
turn the link error into a load-time one on Android 5.1/6.0, so define the
two symbols instead, using the RTM_GETLINK + RTM_GETADDR netlink dump bionic
itself uses. The definition also shadows bionic's on API >= 24 rather than
delegating to it, so the path that ships is the path every test device runs.

Checked against synthesised netlink dumps on the host -- link/address parsing,
prefix masks, point-to-point, ipv6 scope ids, malformed and truncated messages
-- under UBSan and byte-exact guard malloc, with a deliberately unsigned
remainder as the negative control.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix three ways ws + WebRTC could not work in practice

Review of #15684 and hbb_common#579. Each of these left the code reading
correct while the feature did not function.

- The RelayResponse race classified P2P with `result.2 == "IPv6"`, but
  that site's futures are only ever the relay ("Relay"/"WebSocket") and
  the WebRTC branch's own "WebRTC" — so the predicate was constantly
  false. When the relay landed first the result was still right (the
  webrtc arm's `others_fut.is_none()` fallback), but when WebRTC
  connected FIRST it was parked as if it were a relay and the relay was
  committed on arrival, discarding a live direct connection. That is the
  LAN case: the better the network, the worse the outcome. Classify by
  what the label means, via is_direct_transport, and test both orderings
  — only the relay-first one was covered.

- handle_peer_info wrote "force-always-relay=Y" into the peer's saved
  config whenever force_relay was set, which now includes the WebSocket
  transport. One ws session therefore turned the peer into a permanent
  relay-by-policy peer, and relay-by-policy means Relay-only ICE, so
  WebRTC could never go direct to it again — the flagship path worked
  exactly once. Persist policy_relay, which is the user's choice; the
  transport is a property of this client, not of the peer.

- The answerer gated on this machine's enable-webrtc option, but that is
  LocalConfig: the UI process writes it and never syncs it over IPC,
  while handle_punch_hole runs in the server process, which on Windows
  resolves LocalConfig under a different profile and reads the
  private-server default of "N". The gate refused to answer in exactly
  the self-hosted deployments the transport exists for. Drop it: the
  answerer follows the request, like the udp/ipv6 legs, and the option
  still gates the feature where it can — an offer only exists because
  some controller had it enabled.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: close without an await point; do not report an unknown path as direct

- close_webrtc is no longer async (hbb_common 88f965f), so the ten call
  sites in port_forward and io_loop - all inside select! arms or futures
  the UI can abandon - can no longer be cancelled mid-teardown, which
  left the pc unclosable and its session entry stranded. Client's own
  spawn_close_webrtc went with it: the runtime-teardown guard it existed
  for now lives in close_detached, so both Drop paths share one
  implementation.

- webrtc_relayed() returns None when no candidate pair is selected or
  the pc closed under a concurrent teardown, and both call sites read
  that as "not relayed", i.e. direct. A TURN-relayed session could
  therefore be shown to the user as peer-to-peer. Claiming a direct path
  needs evidence of one, so an unknown answer now counts as relayed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* scrap/benchmark: give the Duration divisor an explicit u32

The webrtc feature pulls time 0.3 into scrap's graph (hbb_common ->
webrtc -> webrtc-dtls -> der-parser -> asn1-rs), and that crate carries
an `impl Div<time::Duration> for std::time::Duration`. Orphan rules
allow it because the RHS is its own type, and trait impls are visible
across the whole dependency graph without a use, so std::time::Duration
now has two Div candidates. `yuv_count as _` casts to a plain inference
variable, which both candidates fit, so it stops resolving:

  error[E0282]: type annotations needed
    --> libs/scrap/examples/benchmark.rs:146:33

Only two of the four sites are reported - rustc emits one E0282 per
function body - so all four are annotated. The already-explicit
`as u32` at the hwcodec site and `start.elapsed() / cnt` are unaffected,
the latter because an integer literal's variable can only unify with an
integral type and rules the time impl out on its own.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* webrtc: judge the race by the resolved path, not the label; bound the ICE queue

Third review round. Two of these are regressions from the previous one.

- The RelayResponse race predicate was `is_direct_transport(result.2)`,
  which answers true for the label "WebRTC" - but WebRTC is only a
  direct path when ICE nominated a non-TURN pair. A TURN-relayed WebRTC
  result therefore committed instantly and cancelled the IPv6 attempt
  racing beside it, which is the same inversion the previous fix removed
  in the other direction. (That fix was also argued from a wrong premise:
  the site does carry an IPv6 future, pushed ~50 lines earlier than the
  relay one.) Each future now resolves whether its path is direct and
  the predicate reads that bool, matching the outer race, and the
  downstream recomputation goes away.

- policy_relay still folded in Config::is_proxy(), and that is what gets
  persisted into the peer's config as force-always-relay - so one
  session through a proxy pinned the peer to relay forever and disabled
  WebRTC for it, exactly the latch the previous round fixed for
  WebSocket. Split out peer_relay: the saved option or an explicit
  request for THIS peer, and the only part written back.

- The controlled side buffered remote ICE candidates in an unbounded
  channel while the controller caps the same buffer at 64, and draining
  one costs a JSON parse plus the ICE agent's lock. Whoever can reach a
  session's route could grow it without limit inside the long-lived
  service process. Bounded, with the overflow logged through the
  existing throttle.

- That route was also removed by key alone when an answerer finished, so
  a punch retry that built a fresh answerer under the same fingerprint
  had its live sender deleted by the previous one's cleanup - after
  which it received no candidates at all. Evict only our own sender, the
  way the session cache already guards the analogous case.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: trim the comments to AGENTS.md length; drop is_direct_transport

386 added comment lines down to 287 across client, mediator, kcp_stream
and common. Same rule as hbb_common 3d64e43: out go past-bug narration,
rejected alternatives, measurements and restatements of the code; the
non-derivable why stays.

is_direct_transport goes with them. Judging the race by a transport
label was replaced by the resolved direct flag, leaving it used only by
its own test — and, having been inserted between the doc comment and
race_transports_prefer_webrtc, it had also taken that function's
contract with it. Removing it reattaches the doc where it belongs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: fix race edge cases that discard or mislabel a direct connection

Three correctness fixes in the transport race, plus three convention
cleanups.

- race_transports_prefer_webrtc committed a relayed result while a direct
  attempt was still in flight: the others arm returned on
  webrtc_fut.is_none() even with an unfinished direct future, and the
  WebRTC-error arm returned a held relay without checking others_fut. A
  relay is now committed only when nothing direct can still arrive (or
  the window expires); a parked relay is also preferred over composing
  an error when both sides fail. Three regression tests, mutation-checked.

- connect()'s plain select_ok let a TURN-relayed WebRTC win as "first
  success", dropping still-racing UDP/IPv6 direct attempts and reporting
  the relayed pair as direct. It now runs through the same prefer-P2P
  race with each attempt carrying whether its path is direct, and the
  WebRTC future resolves is_relayed() so a TURN win is held behind
  direct attempts, not committed as one.

- The RelayResponse path kept direct == true when a WebRTC win's DTLS
  handshake failed and it fell back to relay, so the relay was reported
  P2P. Clear the flag with the transport switch.

- Trim the OffererGuard doc to the three-line max; move the new
  enable-webrtc localization key to the end of every lang list; the KCP
  option constant moved to hbb_common config::keys (0f663aa).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump hbb_common: WebRTC peer connections own their I/O runtime

Closing the controlling window left the controlled side waiting out
ICE decay — ~25-30s in the peer's log, its disconnected/failed ladder
running to completion — where TCP delivers a FIN at once. The session
end closed the pc by spawning onto io_loop's own
`#[tokio::main(flavor = "current_thread")]` runtime, which is dropped
the moment io_loop returns, and nothing after that call yields: the
task was never polled even once, so no DTLS close_notify ever left.

Every attempt to fix that on the caller's side failed the same way,
because the mismatch was never about where the close ran: a pc's UDP
sockets register with the reactor, and its ICE/DTLS/SCTP pumps spawn
on the runtime, that is current while it is built — so a pc created
by a session outlives the only runtime that can drive its I/O, and a
close driven anywhere else completes without reaching the wire.

The bump homes them where they can outlive any caller: WebRTCStream
builds on a process-lifetime runtime and every detached close runs
there as its own never-cancelled task. io_loop keeps its plain
close_webrtc() calls and only documents why nothing here may spawn or
await the teardown on the dying session runtime.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* fix: give the UDP NAT test a real window when the TCP clock is faked

The punch request carries udp_port only if the rendezvous server's
TestNatResponse has arrived, and the wait for it was bounded by
rtt / 2 — half the TCP connect time, on the assumption that TCP and
UDP round trips are comparable and the test, started earlier, has
already answered.

A transparent TCP proxy breaks that assumption: a TUN-mode VPN on the
host, or a redirect-mode proxy on the LAN gateway serving every device
behind it, completes the handshake locally in ~3ms while the real UDP
round trip is hundreds of ms. Log-confirmed against 5.161.65.208: ping
341ms, TCP connect 3.7ms, connect to a dead port there "succeeds" just
as fast. The window collapsed to ~1.5ms, udp_port stayed 0 on every
attempt, and UDP punch was never even requested — although UDP itself
passes such gateways untouched.

So use the TCP clock only when it is believable: below a plausible WAN
round trip it says nothing about the UDP path, and a flat ceiling
applies instead. The loop still exits the moment the port arrives, so
a genuinely nearby server pays nothing and only a UDP-dead network
waits out the ceiling — on the udp-carrying round alone, while the
parallel pure-TCP round is unaffected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* feat: make the TCP punch a user option, with TCP as the backstop

TCP punching was the one direct transport without a switch, while UDP,
IPv6 and WebRTC each had one. Add "Enable TCP hole punching" above the
UDP toggle on both desktop and mobile, default on — including on
self-hosted servers, since unlike the other three (whose default-off
there guards against an hbbs that cannot forward their fields) TCP
punching has always been supported by every server.

Turning all four off would leave no way to punch at all, so TCP runs
regardless in that case. That backstop keys off the switches alone: a
transport that is enabled but fails to materialize — no public v6
address, no NAT port, a failed offerer — is already covered by the
relay fallback for a round that ends up with no usable direct
transport. With the TCP punch off, the fallback request is skipped
too: it exists only to carry that punch, and would otherwise reach
connect() with nothing to try and merely open a second relay.

Known cost, unchanged behavior for the peer: the request carries no
field for this choice, so a peer that receives one with no udp_port and
no offer still punches a TCP hole and listens for a connection the
controller will not make. Representing the transport choice on the
wire needs a proto field and the server forwarding it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* bump hbb_common: name the punch by every transport it carries

`get_local_endpoint_trickle` became `local_endpoint() -> &str`, which
cannot fail, so both call sites lose an unreachable error arm — the
mediator's closed a pc against a failure that no longer exists.

`punch_type` named one transport, and picked it off `allow_tcp_punch`.
A round carries several at once — a NAT port and a v6 address and an
offer — and since the TCP punch became a switch it can carry none, so
one name had to misreport both: the logs of the round that broke WebRTC
read "#1 UDP punch attempt" while the request also carried the v6
address and the offer that was actually failing, and a round with
nothing to punch with was labelled "WebRTC". List them instead —
"UDP+IPv6+WebRTC" — and call the empty round "Relay", which is what it
can still end as and what `typ` prints for it.

The offer is moved into the request rather than cloned into it; that
was its last use.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: drop link-local IPv6 from ICE gathering

Also pin webrtc-util to a fork of 0.11.0 carrying a Windows IPv6 enumeration fix.
`ifaces` reads the adapter list's on-wire IPv6 bytes as host-order `[u16; 8]`, so on a
little-endian host every group comes out byte-swapped and unbindable: a peer's real
240e:369:9606:4600:f52a:7a8d:2530:4de0 is enumerated as e24:6903:696:46:2af5:8d7a:3025:e04d,
::1 as ::100 and fe80:: as 80fe::. Each fails to bind with WSAEADDRNOTAVAIL, so ICE gathers
no IPv6 host candidate at all on Windows - where a globally routable address is the one
NAT-free path a CGNAT'd peer has.

Never reported upstream; the unix twin of the same bug was fixed in webrtc-rs#475 (2023).
Fork: rustdesk-org/webrtc, branch rustdesk-patches, tag webrtc-util-0.11.0-win-ipv6.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: name the family a WebRTC session runs over

`stream_type` reaches the UI as the transport that won the race, and every other transport
already carries the family in that label - the v6 punch reports `IPv6`. WebRTC does not: one
label covers both families, and it is the one path whose real remote address can differ from
the rendezvous-observed one the session is identified by.

Refine it at the hand-off to the UI rather than at the source: five sites in client.rs
compare `typ == "WebRTC"`, so widening the label there would silently move control flow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: one STUN list, and drop the dead IPv4 half

`test_ipv6` kept its own hand-written copy of the STUN servers. It now reads
`WebRTCStream::stun_servers()`, so an operator who points OPTION_ICE_SERVERS at their own
server gets it on both paths instead of one.

`test_bind_ipv6` sends nothing - `connect` only makes the kernel pick a route and a source
address - so the whole cost is DNS. It races the lookups rather than betting this host's
IPv6 support on whether the first entry happens to publish a AAAA where the user resolves
from; google's does not, from a Chinese resolver, and it was the entry being bet on.

`stun_ipv4_test`, `STUNS_V4` and `test_nat_ipv4` have had no callers since the punch stopped
taking its port from a second socket, and go.

`get_kcp_cc_enabled` reads the renamed option through `option2bool`, like every other one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* webrtc: take dcsctp's retransmission timings and IPv6-safe MTU

webrtc-sctp ships RFC 4960's RTO.Initial/RTO.Min (3000/1000), TCP's values for
arbitrary public paths. On this workload they set the recovery time outright:
a request/response exchange keeps one chunk in flight, so no later SACK ever
raises miss_indicator to the 3 that arms fast retransmit, and the T3 floor is
the only way back. A single loss during a handshake or a first keyframe
therefore costs whole seconds.

The fork now carries dcsctp's numbers instead - the SCTP implementation Google
wrote to replace usrsctp for Chrome's WebRTC data channels, the same realtime
workload: rto_initial 500, rto_min 400, a 220ms floor under the RTT variance,
and mtu 1191. INITIAL_MTU 1228 plus DTLS/UDP/IPv6 overhead is 1313, past the
1280 minimum, so every full-size chunk fragmented on an IPv6 path.

Both patch entries move to the new branch, which also carries the Windows IPv6
byte-swap fix, so one rev matches the whole webrtc 0.13 stack.

* udp: make the punch prove itself, and keep the listener answering

punch_udp sent a zero-length datagram and called the hole open on whatever
arrived next. The rendezvous NAT test's own leftover replies satisfy that
immediately - connect() does not flush the receive queue - so the retry loop
never ran and success meant nothing. The dead socket then cost KCP its full
timeout to rediscover, which is how a failed punch came to take 18 seconds.

Probes now carry a magic and a 64-bit transaction id, and both ends answer
each other's probes, so returning is a fact: a reply echoing our own id is the
one thing that proves the pair carries traffic both ways. With failure now
distinguishable from 'not yet', the window drops from 20s to 3s.

Two asymmetries fall out of that:

Only the connector stops on its own acknowledgement, because only it has
something to send next. An acknowledgement proves our probe came back, not
that the peer's probe was answered - and after punch_udp returns nothing
answers probes any more, since KCP's io loop drops anything shorter than its
header. A listener that stopped there would go mute while a peer whose own
probe or answer was lost - the normal state of a hole still opening - kept
probing an endpoint that works, until it timed out.

So the listener stops on the peer's first real packet instead, and hands that
packet to KcpStream::accept as its init_packet: its arrival proves the pair as
well as an acknowledgement would, and KCP never retransmits its SYN.

* webrtc: correct the RTT variance floor to dcsctp's scaling

The earlier commit took dcsctp's min_rtt_variance = 220 as a raw floor under
rttvar. dcsctp divides the option by kHeuristicVarianceAdjustment = 8.0 first,
a historical accident it kept because downstream users had measured good
values with it, so the intended floor is 27.5ms of variance contributing 110ms
to RTO. Flooring at 220 contributed 880ms instead, which on a 50ms path left
RTO within 7% of the 1000ms default this change exists to escape.

The fork also now records why T1/T2 share T3's RTO manager here, unlike
dcsctp's separate control timers: RTO_INITIAL is the T3 value for the first
DATA chunk, since no RTT sample exists before the first SACK.

* webrtc: skip the controller's ICE re-send instead of queueing it twice

The controller sends every candidate twice, because the server's hop to a
peer registered over UDP can lose one. The ICE agent that dedups repeats
sits downstream of the answerer's queue, so the answerer paid for both
copies: a slot, a JSON parse, and the ICE agent's lock, once per repeat.

Remember a digest of what was queued and skip the repeat. Recorded only
once queued, so a candidate a full queue refused stays repairable by the
re-send.

The queue's depth is unchanged. A real peer gathers well under it - four
STUN servers, link-local IPv6 filtered, one component - and the drain
empties it as candidates trickle in, so what this removes is the redundant
work, not an overflow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* tcp: repeat the punch across the controller's dial window

The single punch leaves before hbbs has told the controller where to dial, so
it is never in flight at the same time as the controller's SYN: it opens our
NAT, meets nothing, and a gateway that answers it with RST takes the mapping
down with it, leaving the listener waiting on a hole that no longer exists.

Punch again while the controller may still be dialing, and race those punches
against the accept. That is two ways in where there was one: the mapping is
rebuilt if a RST took it, and once the controller sits in SYN_SENT one of the
punches meets its SYN and completes as a simultaneous open - which a punch sent
before the controller had been told anything never could. The crossing reaches
the punch rather than the listener because the two sockets share the address
but only the punch matches the four-tuple, which the tests now pin down.

There is no instant to aim at, and no window either. `Client::connect` sizes
the controller's dial only after our PunchHoleSent, from its own rendezvous
time and the direct failures it has recorded for us: CONNECT_TIMEOUT between
two known-asymmetric NATs that never failed, punch_time_used times three or
six otherwise, floored at a second - so a peer that failed once dials for a
second or two from then on, and none of that reaches this side. The repeats
therefore cover our own ceiling instead, CONNECT_TIMEOUT, which is exactly as
long as the accept has always been willing to take a connection through the
hole, and back off across it: dense at the start, where every window begins
and the short ones end, sparse afterwards, which is `punch_udp`'s shape for
the same reason. A window past that ceiling was lost before this change too,
and mostly to the controller's own kernel - Windows gives a SYN up at 21s,
Linux's next re-send after 15s is at 31s; a window short of it costs a few
SYNs to a port already closed.

No punch is cut on a per-attempt timeout; one in flight is bounded only by
the shared deadline plus PUNCH_GRACE. A punch is cancel-safe only while it is
still in SYN_SENT; once the controller's SYN has crossed it the socket is half
way through a handshake, and cutting it there cuts the connection the
controller is opening - whose `connect` has already returned, so that attempt
fails outright, there being no relay fallback after a failed TCP handshake. A
timer cannot tell the two states apart, and none is needed: a gateway that
answers with RST fails the connect at once and the loop punches again, while
one that drops the SYN in silence leaves the socket in SYN_SENT, holding the
mapping open while the kernel re-sends, which any SYN of the controller's then
crosses - a second punch has nothing to add. The deadline decides whether
another punch starts; one in flight runs a grace past it, enough for a
crossing begun just before it to complete. The last sleep is cut at the
deadline rather than run out past it, so the window ends on a punch given
that grace and not on a gap of up to the backoff ceiling: the controller's
window opened after ours, on the PunchHoleSent hbbs relayed, so one as long
as ours is still open through our tail.

Only the accept races the punch, never `accept_connection`: that one does not
return until the session it goes on to run has ended, so racing it would tear a
live session down.

Whichever arrives first is the one connection the request produces. `meta`
carries the control permissions hbbs granted for this one controller, so
serving the loser as well would hand them to a second peer - and nothing about
a connection tells the two apart before `create_tcp_connection` has spoken to
it, least of all its address: a carrier NAT shares one between subscribers,
and a NAT that pools its external addresses may dial us from a different one
than hbbs saw the controller through. So the address is not checked, as
`accept_connection` never checked it; the handshake says who arrived, and what
holds the invariant is that there is no second serve. Those
permissions are a ceiling and not a grant either way: `Connection` gates every
message on `authorized`, and latches the login scope of the first request it
accepts, so a peer that reached the hole still arrives with nothing.

The accept loops rather than taking a single connection, so that a transient
accept error does not spend the window the controller still has to arrive in.

libp2p's DCUtR reaches the same place by having both peers dial at one instant
agreed over the relay. Nothing we send reaches the controller directly, so we
cover its dial window rather than name an instant inside it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* hbb_common: bump to the webrtc branch rebased on main

Picks up upstream's session-cache eviction by pc identity (#589, adopted without its
unused insert-path helper), the 90-day log retention, and the wlroots output fixes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* webrtc: send over SCTP without a congestion window, as KCP does

The same link that streams over KCP crawls over WebRTC. webrtc-sctp runs
RFC 4960's AIMD: a fast retransmit halves cwnd, a T3 drops it to one MTU, and
slow start only rebuilds it while data is queued behind it. Where the loss is
random rather than congestion - a lossy long-haul link - the rate settles at
the Mathis ceiling MSS/(RTT*sqrt(p)) however idle the link is: about 1.3 Mbps
at 70ms RTT and 1% loss, 0.6 Mbps at 5%, while 1080p wants 2-5 Mbps. KCP's
turbo profile (nc=1) has no congestion window at all.

The fork now carries a switch that bypasses the two places gating sends on
cwnd, and hbb_common turns it on for every peer connection unless
`allow-webrtc-congestion-control` is set - the same opt-in KCP has in
`allow-kcp-congestion-control`, for the reason at `get_kcp_cc_enabled`.
Sender-side only; a browser or an older build on the other end interoperates.

Measured over a simulated link (35ms one-way, random loss both ways, 12 KB
frames at 30fps, 300 frames): at 1% loss the window stretches 9.9s of video to
20.7s with a mean latency of 5.5s; without it the stream stays realtime at a
mean of 113ms. At 3%: 47s and 15s against 10.2s and 290ms.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* webrtc: take the fork's loss recovery for sending without a congestion window

rustdesk-org/webrtc 825a0a48: without a congestion window a chunk is lost
once three chunks sent after its latest transmission are acked, counted in
send order so retransmitted chunks are covered too, and the fast retransmit
sends every lost chunk at once, as KCP nc=1 does; before, a lost
retransmission waited for T3-rtx. Also fixes the delayed SACK timer never
re-arming, the switch applying to established associations, T3-rtx
resending one chunk when the peer's window is full, and bounds new data to
1 MiB / 1024 chunks in flight like KCP's snd_wnd.

Simulated 35ms one-way, random loss both ways, 30 fps, frames later than
200ms out of 1200: 12 KB at 5% loss 996 -> 55 (KCP 61); 40 KB at 2% loss
1183 -> 20 (KCP 39).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump hbb_common: decode TURN userinfo, add the webrtc_echo example

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXJJGEGdgu26wgCppvUXdZ

* web: show the WebRTC toggle and transport in the web UI

The web client now speaks WebRTC, but the desktop settings page hides
the punch options on web and the remote page opens without the session
tab that carries the transport name. Let the existing "Enable WebRTC P2P
connection" checkbox through on web (the other punch options stay
native-only), and add a Transport row to the quality monitor for WebRTC
sessions only (with "(TURN)" when ICE relayed), on every platform.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXJJGEGdgu26wgCppvUXdZ

* bump hbb_common: end the ICE forwarder at gathering complete, drop the closes Drop covers

hbb_common now closes the local-candidate channel when gathering
completes, so the controlled side's forwarder in spawn_webrtc_answerer
ends there, and its signaling connection to hbbs with it, instead of
sitting on a socket hbbs closed at 90s idle for the rest of the session.
It also keeps the reassembly buffer across fragmented frames.

Stream closes the WebRTC peer connection on drop (hbb_common b0b624d),
so the close_webrtc() calls in port_forward and io_loop that sat
immediately before a return or the end of scope did nothing Drop was
not about to do, while the comments beside them still said a bare drop
leaked the pc. Remove both.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump hbb_common: quiet the webrtc-rs warnings that describe the race's normal outcome

Cancelling the transport that lost the race, and trickle checking before it
holds a pair, are what the design does on every session that connects - and
webrtc-rs reports both at warn, 90 lines of a 386-line controlled-side log,
beside connections that succeeded. agent_internal and peer_connection drop to
error; agent_gather keeps warn, since an unreachable STUN server is the one
upstream signal that explains a session which never connected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M54JAqUK4RynudFou89hod

* port_forward: restore the `?` the close removal left as a match

Dropping the explicit close_webrtc() from the parse-error arm left a match
that only re-spells `?`; master just reworked this function, so the branch
now leaves port_forward.rs untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* l10n: the two WebRTC keys were missing from Urdu

Every other lang file on the branch carries them; ur.rs was skipped when
they were added.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* udp: make the punch deadline absolute, so a talking peer cannot defer it

`select!` rebuilds every arm each iteration, so the relative retry sleep was
restarted by each datagram that arrived before it fired. The peer sets that
rate, and an old-build peer's empty datagrams match no arm and loop without
even the recv-error pause, so MAX_TIME went unchecked and the retransmit was
starved with it. `udp_nat_connect` awaits the punch ahead of the KCP timeout
and nothing above it bounds the phase, so the punch held the direct race open
and the relay fallback out of reach for as long as the peer kept sending.

Absolute instants for both clocks. The new test floods empty datagrams for
four times the deadline: the punch now ends at 3s where it ran the full 12s.

Also note at the symmetric-NAT branch that WebRTC not following the legacy
relay decision there is deliberate, so it is not later "fixed" into agreement.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: MTU-safe bundles, a reordering window, tail loss within the RTT

rustdesk-org/webrtc cc6633bc, three commits on 825a0a48, all on the path
that sends without a congestion window:

Both bundlers counted a DATA chunk by its payload alone; with the header and
padding counted, bundles of small chunks stay within the MTU, and the fragment
payload rounds down to 1160 so a full chunk does too. A chunk is fast
retransmitted at most five times, KCP's IKCP_FASTACK_LIMIT.

A frame's chunks go out within microseconds of each other, so on a path that
jitters the send-order rule resent every chunk that landed behind three of
its siblings: 2.7x the payload on the wire at 10ms of jitter, and on a link
without the room for that, a queue that fed on itself. A reordering window,
RACK's, makes evidence count only from what was sent a quarter of an srtt
after the chunk once the path is seen to reorder, widening on the duplicate
TSNs the receiver reports. 5 Mbps, 1% loss, 20ms jitter: 600 of 600 frames
at a 98ms mean where 290 arrived at 6.2s.

A chunk lost at the tail of a burst has only T3-rtx, which ran from floors
sized for a 200ms delayed ack and restarted only on the tail's predecessor's
ack: 600ms and more. Every DATA chunk now carries the I bit, the floors are
KCP's shape, and a fast retransmission restarts the timer. One 200-byte
message per frame at 5% loss: 9 of 600 later than 200ms, from 42.

Random loss without jitter is unchanged at every rate and frame size.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: T3-rtx restarts only for the earliest chunk's fast retransmission

rustdesk-org/webrtc 2b8e55bc. Sending without a congestion window, a fast
retransmission of any chunk restarted T3-rtx, so a chunk past the fast
retransmission cap - left to that timer - never reached it while later
chunks kept being resent, which a lossy stream does every couple of frames.
The timer is the earliest in-flight chunk's, and only its resend restarts
it now. Nothing else changes; the benchmark is unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: T3-rtx restart on fast retransmission while shutting down too

rustdesk-org/webrtc 48100bf1. The restart for the earliest chunk's fast
retransmission reached only the Established branch of the write loop; the
shutdown states still carry data in flight and recover it the same way, so a
closing association could still resend everything on a loss its fast
retransmit had already recovered. Both branches share one helper now.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-09-06 00:21:28 +08:00
8 changed files with 826 additions and 13 deletions

View File

@@ -2300,6 +2300,16 @@ jobs:
# build rustdesk
python3 ./res/inline-sciter.py
export CARGO_INCREMENTAL=0
# armv7 is the only 32-bit target in this job that links the whole binary, and the
# release profile uses fat LTO with codegen-units=1. LLVM then merges every module
# into a single unit and runs past the ~3GB address space a 32-bit process gets,
# aborting rustc with "Rust cannot catch foreign exceptions" (a C++ bad_alloc from
# LLVM unwinding into rustc's Rust frames). Thin LTO keeps peak memory bounded and
# still allows cross-crate inlining; 64-bit targets keep fat LTO untouched.
if [ "${{ matrix.job.arch }}" = "armv7" ]; then
export CARGO_PROFILE_RELEASE_LTO=thin
export CARGO_PROFILE_RELEASE_CODEGEN_UNITS=16
fi
cargo build --locked --features inline${{ matrix.job.extra_features }} --release --bins --jobs 1
# make debian package
mkdir -p ./Release

4
Cargo.lock generated
View File

@@ -9708,7 +9708,7 @@ dependencies = [
[[package]]
name = "webrtc-sctp"
version = "0.12.0"
source = "git+https://github.com/rustdesk-org/webrtc?rev=48100bf13e694d7e5bbb49b9a753dbad1c359d0c#48100bf13e694d7e5bbb49b9a753dbad1c359d0c"
source = "git+https://github.com/rustdesk-org/webrtc?rev=b221f13b1d6f21fbce09f9f63096be27dd392265#b221f13b1d6f21fbce09f9f63096be27dd392265"
dependencies = [
"arc-swap",
"async-trait",
@@ -9748,7 +9748,7 @@ dependencies = [
[[package]]
name = "webrtc-util"
version = "0.11.0"
source = "git+https://github.com/rustdesk-org/webrtc?rev=48100bf13e694d7e5bbb49b9a753dbad1c359d0c#48100bf13e694d7e5bbb49b9a753dbad1c359d0c"
source = "git+https://github.com/rustdesk-org/webrtc?rev=b221f13b1d6f21fbce09f9f63096be27dd392265#b221f13b1d6f21fbce09f9f63096be27dd392265"
dependencies = [
"async-trait",
"bitflags 1.3.2",

View File

@@ -224,10 +224,13 @@ libxdo-sys = { path = "libs/libxdo-sys-stub" }
# a congestion window, as KCP does - on by default, `allow-webrtc-congestion-control` opts back in.
# Sending that way, a reordering window keeps a chunk that is merely late from being resent on a
# path that jitters, every DATA chunk asks for its SACK at once so a lost tail is back within an
# RTT at KCP's RTO floors, and bundles of small chunks stay within the MTU.
# RTT at KCP's RTO floors, and bundles of small chunks stay within the MTU. A T3-rtx resends
# everything outstanding when it packs into four packets and otherwise probes with one and lets
# the SACK settle the rest (F-RTO), timed from the latest send, so a stall no longer resends the
# whole backlog behind itself while a short lost tail still comes back at once.
# Pinned by rev, not branch: a fork branch can be rewritten out from under the lockfile.
webrtc-util = { git = "https://github.com/rustdesk-org/webrtc", rev = "48100bf13e694d7e5bbb49b9a753dbad1c359d0c" }
webrtc-sctp = { git = "https://github.com/rustdesk-org/webrtc", rev = "48100bf13e694d7e5bbb49b9a753dbad1c359d0c" }
webrtc-util = { git = "https://github.com/rustdesk-org/webrtc", rev = "b221f13b1d6f21fbce09f9f63096be27dd392265" }
webrtc-sctp = { git = "https://github.com/rustdesk-org/webrtc", rev = "b221f13b1d6f21fbce09f9f63096be27dd392265" }
[package.metadata.winres]
LegalCopyright = "Copyright © 2026 Purslane Tech Pte. Ltd. All rights reserved."

View File

@@ -698,7 +698,7 @@ mod proto {
let content = if compress {
compressed
} else {
s.bytes().collect::<Vec<u8>>()
d
};
Clipboard {
compress,
@@ -794,6 +794,29 @@ mod proto {
msg
})
}
#[cfg(all(test, not(target_os = "android")))]
mod tests {
use super::{from_clipboard, special_to_proto};
use arboard::ClipboardData;
#[test]
fn preserves_uncompressed_special_clipboard_data() {
let data = vec![0x01, 0x02, 0x03];
let name = "custom-format".to_owned();
let clipboard = special_to_proto(data.clone(), name.clone());
assert!(!clipboard.compress);
assert_eq!(clipboard.content.as_ref(), data.as_slice());
assert_eq!(clipboard.special_name, name);
assert!(matches!(
from_clipboard(clipboard),
Some(ClipboardData::Special((restored_name, restored_data)))
if restored_name == name && restored_data == data
));
}
}
}
#[cfg(all(test, not(target_os = "android")))]

View File

@@ -51,6 +51,7 @@ mod ta;
mod ge;
mod fi;
mod ml;
mod gl;
pub const LANGS: &[(&str, &str)] = &[
("en", "English"),
@@ -84,6 +85,7 @@ pub const LANGS: &[(&str, &str)] = &[
("ur", "اردو"),
("fa", "فارسی"),
("ca", "Català"),
("gl", "Galego"),
("el", "Ελληνικά"),
("sv", "Svenska"),
("sq", "Shqip"),
@@ -217,6 +219,7 @@ pub fn translate_locale(name: String, locale: &str) -> String {
"ml" => ml::T.deref(),
"hi" => hi::T.deref(),
"gu" => gu::T.deref(),
"gl" => gl::T.deref(),
_ => en::T.deref(),
};
let (name, placeholder_value) = extract_placeholder(&name);

774
src/lang/gl.rs Normal file
View File

@@ -0,0 +1,774 @@
lazy_static::lazy_static! {
pub static ref T: std::collections::HashMap<&'static str, &'static str> =
[
("Status", "Estado"),
("Your Desktop", "O teu escritorio"),
("desk_tip", "Pódese acceder ao teu escritorio con este ID e contrasinal."),
("Password", "Contrasinal"),
("Ready", "Listo"),
("Established", "Establecido"),
("connecting_status", "Conectando á rede de RustDesk..."),
("Enable service", "Activar o servizo"),
("Start service", "Iniciar o servizo"),
("Service is running", "O servizo está a executarse"),
("Service is not running", "O servizo non se está a executar"),
("not_ready_status", "Non está listo. Comproba a túa conexión"),
("Control Remote Desktop", "Controlar o escritorio remoto"),
("Transfer file", "Transferir ficheiro"),
("Connect", "Conectar"),
("Recent sessions", "Sesións recentes"),
("Address book", "Caderno de enderezos"),
("Confirmation", "Confirmación"),
("TCP tunneling", "Tunelización TCP"),
("Remove", "Retirar"),
("Refresh random password", "Actualizar o contrasinal aleatorio"),
("Set your own password", "Establecer o teu propio contrasinal"),
("Enable keyboard/mouse", "Activar teclado/rato"),
("Enable clipboard", "Activar portapapeis"),
("Enable file transfer", "Activar transferencia de ficheiros"),
("Enable TCP tunneling", "Activar tunelización TCP"),
("IP Whitelisting", "Lista branca de IP"),
("ID/Relay Server", "Servidor de ID/retransmisión"),
("Import server config", "Importar configuración do servidor"),
("Export Server Config", "Exportar configuración do servidor"),
("Import server configuration successfully", "A configuración do servidor importouse correctamente"),
("Export server configuration successfully", "A configuración do servidor exportouse correctamente"),
("Invalid server configuration", "Configuración do servidor non válida"),
("Clipboard is empty", "O portapapeis está baleiro"),
("Stop service", "Deter o servizo"),
("Change ID", "Cambiar ID"),
("Your new ID", "O teu novo ID"),
("length %min% to %max%", "lonxitude de %min% a %max%"),
("starts with a letter", "comeza cunha letra"),
("allowed characters", "caracteres permitidos"),
("id_change_tip", "Só se permiten caracteres a-z, A-Z, 0-9, - (guión) e _ (guión baixo). A primeira letra debe ser a-z, A-Z. Lonxitude entre 6 e 16."),
("Website", "Sitio web"),
("About", "Sobre"),
("Slogan_tip", "Feito con agarimo neste mundo caótico!"),
("Privacy Statement", "Declaración de privacidade"),
("Mute", "Silenciar"),
("Build Date", "Data de compilación"),
("Version", "Versión"),
("Home", "Inicio"),
("Audio Input", "Entrada de audio"),
("Enhancements", "Melloras"),
("Hardware Codec", "Códec por hardware"),
("Adaptive bitrate", "Taxa de bits adaptativa"),
("ID Server", "Servidor de ID"),
("Relay Server", "Servidor de retransmisión"),
("API Server", "Servidor de API"),
("invalid_http", "debe comezar con http:// ou https://"),
("Invalid IP", "IP non válida"),
("Invalid format", "Formato non válido"),
("server_not_support", "Aínda non admitido polo servidor"),
("Not available", "Non dispoñíbel"),
("Too frequent", "Demasiado frecuente"),
("Cancel", "Cancelar"),
("Skip", "Omitir"),
("Close", "Pechar"),
("Retry", "Tentar de novo"),
("OK", "Aceptar"),
("Password Required", "Requírese contrasinal"),
("Please enter your password", "Por favor, introduce o teu contrasinal"),
("Remember password", "Lembrar o contrasinal"),
("Wrong Password", "Contrasinal incorrecto"),
("Do you want to enter again?", "Queres tentalo de novo?"),
("Connection Error", "Erro de conexión"),
("Error", "Erro"),
("Reset by the peer", "Restablecido polo par"),
("Connecting...", "Conectando..."),
("Connection in progress. Please wait.", "Conexión en curso. Por favor, agarda."),
("Please try 1 minute later", "Por favor, téntao 1 minuto máis tarde"),
("Login Error", "Erro de inicio de sesión"),
("Successful", "Feito correctamente"),
("Connected, waiting for image...", "Conectado, agardando pola imaxe..."),
("Name", "Nome"),
("Type", "Tipo"),
("Modified", "Modificado"),
("Size", "Tamaño"),
("Show Hidden Files", "Amosar ficheiros ocultos"),
("Receive", "Recibir"),
("Send", "Enviar"),
("Refresh File", "Actualizar ficheiro"),
("Local", "Local"),
("Remote", "Remoto"),
("Remote Computer", "Computador remoto"),
("Local Computer", "Computador local"),
("Confirm Delete", "Confirmar eliminación"),
("Delete", "Eliminar"),
("Properties", "Propiedades"),
("Multi Select", "Selección múltiple"),
("Select All", "Seleccionar todo"),
("Unselect All", "Deseleccionar todo"),
("Empty Directory", "Directorio baleiro"),
("Not an empty directory", "Non é un directorio baleiro"),
("Are you sure you want to delete this file?", "Tes a certeza de que queres eliminar este ficheiro?"),
("Are you sure you want to delete this empty directory?", "Tes a certeza de que queres eliminar este directorio baleiro?"),
("Are you sure you want to delete the file of this directory?", "Tes a certeza de que queres eliminar o ficheiro deste directorio?"),
("Do this for all conflicts", "Facer isto para todos os conflitos"),
("This is irreversible!", "Isto é irreversíbel!"),
("Deleting", "Eliminando"),
("files", "ficheiros"),
("Waiting", "Agardando"),
("Finished", "Rematado"),
("Speed", "Velocidade"),
("Custom Image Quality", "Calidade de imaxe personalizada"),
("Privacy mode", "Modo de privacidade"),
("Block user input", "Bloquear a entrada do usuario"),
("Unblock user input", "Desbloquear a entrada do usuario"),
("Adjust Window", "Axustar ventá"),
("Original", "Orixinal"),
("Shrink", "Reducir"),
("Stretch", "Axustar"),
("Scrollbar", "Barra de desprazamento"),
("ScrollAuto", "Desprazamento automático"),
("Good image quality", "Boa calidade de imaxe"),
("Balanced", "Equilibrada"),
("Optimize reaction time", "Optimizar tempo de reacción"),
("Custom", "Personalizado"),
("Show remote cursor", "Amosar o cursor remoto"),
("Show quality monitor", "Amosar o monitor de calidade"),
("Disable clipboard", "Desactivar portapapeis"),
("Lock after session end", "Bloquear tras rematar a sesión"),
("Insert Ctrl + Alt + Del", "Inserir Ctrl + Alt + Supr"),
("Insert Lock", "Inserir bloqueo"),
("Refresh", "Actualizar"),
("ID does not exist", "O ID non existe"),
("Failed to connect to rendezvous server", "Produciuse un fallo ao conectar co servidor de cita (rendezvous)"),
("Please try later", "Por favor, téntao máis tarde"),
("Remote desktop is offline", "O escritorio remoto está desconectado"),
("Key mismatch", "As chaves non coinciden"),
("Timeout", "Tempo de espera esgotado"),
("Failed to connect to relay server", "Produciuse un fallo ao conectar co servidor de retransmisión"),
("Failed to connect via rendezvous server", "Produciuse un fallo ao conectar a través do servidor de cita (rendezvous)"),
("Failed to connect via relay server", "Produciuse un fallo ao conectar a través do servidor de retransmisión"),
("Failed to make direct connection to remote desktop", "Produciuse un fallo ao realizar a conexión directa co escritorio remoto"),
("Set Password", "Establecer contrasinal"),
("OS Password", "Contrasinal do SO"),
("install_tip", "Debido ao UAC, RustDesk non pode funcionar axeitadamente como lado remoto nalgúns casos. Para evitar o UAC, preme o botón de abaixo para instalar RustDesk no sistema."),
("Click to upgrade", "Preme para anovar"),
("Configure", "Configurar"),
("config_acc", "Para poder controlar o teu escritorio remotamente, cómpre conceder a RustDesk permisos de «Accesibilidade»."),
("config_screen", "Para poder acceder ao teu escritorio remotamente, cómpre conceder a RustDesk permisos de «Gravación de pantalla»."),
("Installing ...", "Instalando..."),
("Install", "Instalar"),
("Installation", "Instalación"),
("Installation Path", "Ruta de instalación"),
("Create start menu shortcuts", "Crear atallos no menú de inicio"),
("Create desktop icon", "Crear icona no escritorio"),
("agreement_tip", "Ao iniciar a instalación, aceptas o acordo de licenza."),
("Accept and Install", "Aceptar e instalar"),
("End-user license agreement", "Acordo de licenza de usuario final"),
("Generating ...", "Xerando..."),
("Your installation is lower version.", "A túa instalación é dunha versión anterior."),
("not_close_tcp_tip", "Non peches esta ventá mentres esteas a usar o túnel"),
("Listening ...", "Escoitando..."),
("Remote Host", "Equipo remoto"),
("Remote Port", "Porto remoto"),
("Action", "Acción"),
("Add", "Engadir"),
("Local Port", "Porto local"),
("Local Address", "Enderezo local"),
("Change Local Port", "Cambiar o porto local"),
("setup_server_tip", "Para unha conexión máis rápida, configura o teu propio servidor"),
("Too short, at least 6 characters.", "Demasiado curto, polo menos 6 caracteres."),
("The confirmation is not identical.", "A confirmación non é idéntica."),
("Permissions", "Permisos"),
("Accept", "Aceptar"),
("Dismiss", "Descartar"),
("Disconnect", "Desconectar"),
("Enable file copy and paste", "Activar copiar e pegar ficheiros"),
("Connected", "Conectado"),
("Direct and encrypted connection", "Conexión directa e cifrada"),
("Relayed and encrypted connection", "Conexión retransmitida e cifrada"),
("Direct and unencrypted connection", "Conexión directa e sen cifrar"),
("Relayed and unencrypted connection", "Conexión retransmitida e sen cifrar"),
("Enter Remote ID", "Introduce o ID remoto"),
("Enter your password", "Introduce o teu contrasinal"),
("Logging in...", "Iniciando sesión..."),
("Enable RDP session sharing", "Activar compartir sesións de RDP"),
("Auto Login", "Acceso automático (só válido se activas «Bloquear tras rematar a sesión»)"),
("Enable direct IP access", "Activar acceso directo por IP"),
("Rename", "Renomear"),
("Space", "Espazo"),
("Create desktop shortcut", "Crear atallo no escritorio"),
("Change Path", "Cambiar a ruta"),
("Create Folder", "Crear cartafol"),
("Please enter the folder name", "Por favor, introduce o nome do cartafol"),
("Fix it", "Solucionalo"),
("Warning", "Aviso"),
("Login screen using Wayland is not supported", "Non se admite a pantalla de inicio de sesión con Wayland"),
("Reboot required", "Cómpre reiniciar"),
("Unsupported display server", "Servidor de pantalla non admitido"),
("x11 expected", "Esperábase X11"),
("Port", "Porto"),
("Settings", "Axustes"),
("Username", "Nome de usuario"),
("Invalid port", "Porto non válido"),
("Closed manually by the peer", "Pechado manualmente polo par"),
("Enable remote configuration modification", "Activar a modificación remota da configuración"),
("Run without install", "Executar sen instalar"),
("Connect via relay", "Conectar mediante retransmisión"),
("Always connect via relay", "Conectar sempre mediante retransmisión"),
("whitelist_tip", "Só as IP da lista branca poden acceder a min"),
("Login", "Iniciar sesión"),
("Verify", "Verificar"),
("Remember me", "Lembrarme"),
("Trust this device", "Confiar neste dispositivo"),
("Verification code", "Código de verificación"),
("verification_tip", "Enviouse un código de verificación ao enderezo de correo electrónico rexistrado, introduce o código para continuar co inicio de sesión."),
("Logout", "Pechar sesión"),
("Tags", "Etiquetas"),
("Search ID", "Buscar ID"),
("whitelist_sep", "Separadas por coma, punto e coma, espazos ou salto de liña"),
("Add ID", "Engadir ID"),
("Add Tag", "Engadir etiqueta"),
("Unselect all tags", "Deseleccionar todas as etiquetas"),
("Network error", "Erro de rede"),
("Username missed", "Falta o nome de usuario"),
("Password missed", "Falta o contrasinal"),
("Wrong credentials", "Nome de usuario ou contrasinal incorrectos"),
("The verification code is incorrect or has expired", "O código de verificación é incorrecto ou caducou"),
("Edit Tag", "Editar etiqueta"),
("Forget Password", "Esquecín o contrasinal"),
("Favorites", "Favoritos"),
("Add to Favorites", "Engadir a favoritos"),
("Remove from Favorites", "Retirar de favoritos"),
("Empty", "Baleiro"),
("Invalid folder name", "Nome de cartafol non válido"),
("Socks5 Proxy", "Proxy Socks5"),
("Socks5/Http(s) Proxy", "Proxy Socks5/Http(s)"),
("Discovered", "Descubertos"),
("install_daemon_tip", "Para iniciar no arranque do sistema, cómpre instalar o servizo do sistema."),
("Remote ID", "ID remoto"),
("Paste", "Pegar"),
("Paste here?", "Pegar aquí?"),
("Are you sure to close the connection?", "Tes a certeza de que queres pechar a conexión?"),
("Download new version", "Descargar a nova versión"),
("Touch mode", "Modo táctil"),
("Mouse mode", "Modo de rato"),
("One-Finger Tap", "Toque cun dedo"),
("Left Mouse", "Botón esquerdo do rato"),
("One-Long Tap", "Toque longo cun dedo"),
("Two-Finger Tap", "Toque con dous dedos"),
("Right Mouse", "Botón dereito do rato"),
("One-Finger Move", "Mover cun dedo"),
("Double Tap & Move", "Dobre toque e mover"),
("Mouse Drag", "Arrastrar co rato"),
("Three-Finger vertically", "Tres dedos en vertical"),
("Mouse Wheel", "Roda do rato"),
("Two-Finger Move", "Mover con dous dedos"),
("Canvas Move", "Mover lenzo"),
("Pinch to Zoom", "Picar para achegar"),
("Canvas Zoom", "Zoom do lenzo"),
("Reset canvas", "Restablecer lenzo"),
("No permission of file transfer", "Sen permiso de transferencia de ficheiros"),
("Note", "Nota"),
("Connection", "Conexión"),
("Share screen", "Compartir pantalla"),
("Chat", "Conversa"),
("Total", "Total"),
("items", "elementos"),
("Selected", "Seleccionado"),
("Screen Capture", "Captura de pantalla"),
("Input Control", "Control de entrada"),
("Audio Capture", "Captura de audio"),
("Do you accept?", "Aceptas?"),
("Open System Setting", "Abrir axustes do sistema"),
("How to get Android input permission?", "Como obter permisos de entrada en Android?"),
("android_input_permission_tip1", "Para que un dispositivo remoto poida controlar o teu dispositivo Android mediante rato ou táctil, cómpre permitirlle a RustDesk usar o servizo de «Accesibilidade»."),
("android_input_permission_tip2", "Por favor, vai á páxina de axustes do sistema seguinte, busca e entra en [Servizos instalados], e activa o servizo [Entrada de RustDesk]."),
("android_new_connection_tip", "Recibiuse unha nova solicitude de control que desexa controlar o teu dispositivo actual."),
("android_service_will_start_tip", "Activar «Captura de pantalla» iniciará automaticamente o servizo, permitindo que outros dispositivos soliciten conectarse ao teu dispositivo."),
("android_stop_service_tip", "Pechar o servizo pechará automaticamente todas as conexións establecidas."),
("android_version_audio_tip", "A versión actual de Android non admite a captura de audio. Por favor, actualiza a Android 10 ou superior."),
("android_start_service_tip", "Toca en [Iniciar servizo] ou activa o permiso de [Captura de pantalla] para iniciar o servizo de compartir pantalla."),
("android_permission_may_not_change_tip", "Os permisos para as conexións establecidas poden non cambiar ao instante ata que se reconecte."),
("Account", "Conta"),
("Overwrite", "Sobrescribir"),
("This file exists, skip or overwrite this file?", "Este ficheiro xa existe, queres omitilo ou sobrescribilo?"),
("Quit", "Saír"),
("Help", "Axuda"),
("Failed", "Fallou"),
("Succeeded", "Feito correctamente"),
("Someone turns on privacy mode, exit", "Alguén activou o modo de privacidade, saíndo"),
("Unsupported", "Non admitido"),
("Peer denied", "O par denegou a conexión"),
("Peer exit", "O par saíu"),
("Failed to turn off", "Produciuse un fallo ao desactivar"),
("Turned off", "Desactivado"),
("Language", "Idioma"),
("Keep RustDesk background service", "Manter o servizo de RustDesk en segundo plano"),
("Ignore Battery Optimizations", "Ignorar as optimizacións de batería"),
("android_open_battery_optimizations_tip", "Se queres desactivar esta función, vai á páxina seguinte de axustes do aplicativo RustDesk, busca e entra en [Batería] e desmarca [Sen restricións]"),
("Start on boot", "Iniciar no arranque"),
("Start the screen sharing service on boot, requires special permissions", "Iniciar o servizo de compartir pantalla no arranque; require permisos especiais"),
("Connection not allowed", "Conexión non permitida"),
("Legacy mode", "Modo herdado"),
("Map mode", "Modo mapa"),
("Translate mode", "Modo tradución"),
("Use permanent password", "Usar contrasinal permanente"),
("Use both passwords", "Usar ambos os contrasinais"),
("Set permanent password", "Establecer contrasinal permanente"),
("Enable remote restart", "Activar o reinicio remoto"),
("Restart remote device", "Reiniciar o dispositivo remoto"),
("Are you sure you want to restart", "Tes a certeza de que queres reiniciar?"),
("Restarting remote device", "Reiniciando o dispositivo remoto"),
("remote_restarting_tip", "O dispositivo remoto estase a reiniciar. Pecha esta caixa de mensaxe e reconéctate co contrasinal permanente despois dun momento."),
("Copied", "Copiado"),
("Exit Fullscreen", "Saír de pantalla completa"),
("Fullscreen", "Pantalla completa"),
("Mobile Actions", "Accións móbiles"),
("Select Monitor", "Seleccionar monitor"),
("Control Actions", "Accións de control"),
("Display Settings", "Axustes de pantalla"),
("Ratio", "Proporción"),
("Image Quality", "Calidade da imaxe"),
("Scroll Style", "Estilo de desprazamento"),
("Show Toolbar", "Amosar a barra de ferramentas"),
("Hide Toolbar", "Agochar a barra de ferramentas"),
("Direct Connection", "Conexión directa"),
("Relay Connection", "Conexión por retransmisión"),
("Secure Connection", "Conexión segura"),
("Insecure Connection", "Conexión non segura"),
("Scale original", "Escala orixinal"),
("Scale adaptive", "Escala adaptativa"),
("General", "Xeral"),
("Security", "Seguranza"),
("Theme", "Tema"),
("Dark Theme", "Tema escuro"),
("Light Theme", "Tema claro"),
("Dark", "Escuro"),
("Light", "Claro"),
("Follow System", "Seguir o sistema"),
("Enable hardware codec", "Activar códec por hardware"),
("Unlock Security Settings", "Desbloquear os axustes de seguranza"),
("Enable audio", "Activar audio"),
("Unlock Network Settings", "Desbloquear os axustes de rede"),
("Server", "Servidor"),
("Direct IP Access", "Acceso directo por IP"),
("Proxy", "Proxy"),
("Apply", "Aplicar"),
("Disconnect all devices?", "Desconectar todos os dispositivos?"),
("Clear", "Limpar"),
("Audio Input Device", "Dispositivo de entrada de audio"),
("Use IP Whitelisting", "Usar lista branca de IP"),
("Network", "Rede"),
("Pin Toolbar", "Fixar a barra de ferramentas"),
("Unpin Toolbar", "Desfixar a barra de ferramentas"),
("Recording", "Gravación"),
("Directory", "Directorio"),
("Automatically record incoming sessions", "Gravar automaticamente as sesións entrantes"),
("Automatically record outgoing sessions", "Gravar automaticamente as sesións saíntes"),
("Change", "Cambiar"),
("Start session recording", "Iniciar a gravación da sesión"),
("Stop session recording", "Deter a gravación da sesión"),
("Enable recording session", "Activar a gravación de sesións"),
("Enable LAN discovery", "Activar detección na rede local (LAN)"),
("Deny LAN discovery", "Denegar detección na rede local (LAN)"),
("Write a message", "Escribe unha mensaxe"),
("Prompt", "Aviso"),
("Please wait for confirmation of UAC...", "Por favor, agarda pola confirmación do UAC..."),
("elevated_foreground_window_tip", "A ventá actual do escritorio remoto require maiores privilexios para operar, polo que non se pode usar o rato e o teclado temporalmente. Podes pedir ao usuario remoto que minimice a ventá actual ou premer o botón de elevación na ventá de xestión de conexións. Para evitar este problema, recoméndase instalar o software no dispositivo remoto."),
("Disconnected", "Desconectado"),
("Other", "Outro"),
("Confirm before closing multiple tabs", "Confirmar antes de pechar varias pestanas"),
("Keyboard Settings", "Axustes do teclado"),
("Full Access", "Acceso completo"),
("Screen Share", "Compartición de pantalla"),
("ubuntu-21-04-required", "Wayland require Ubuntu 21.04 ou superior."),
("wayland-requires-higher-linux-version", "Wayland require unha versión superior da distribución de Linux. Por favor, proba co escritorio X11 ou cambia de sistema operativo."),
("xdp-portal-unavailable", "Fallou a captura de pantalla en Wayland. É posíbel que o XDG Desktop Portal fallase ou non estea dispoñíbel. Tenta inicialo de novo con `systemctl --user restart xdg-desktop-portal`."),
("JumpLink", "Ver"),
("Please Select the screen to be shared(Operate on the peer side).", "Por favor, selecciona a pantalla que se vai compartir (operar no lado do par)."),
("Show RustDesk", "Amosar RustDesk"),
("This PC", "Este equipo"),
("or", "ou"),
("Elevate", "Elevar"),
("Zoom cursor", "Zoom no cursor"),
("Accept sessions via password", "Aceptar sesións mediante contrasinal"),
("Accept sessions via click", "Aceptar sesións mediante clic"),
("Accept sessions via both", "Aceptar sesións mediante ambos os dous"),
("Please wait for the remote side to accept your session request...", "Por favor, agarda a que o lado remoto acepte a túa solicitude de sesión..."),
("One-time Password", "Contrasinal dun só uso"),
("Use one-time password", "Usar contrasinal dun só uso"),
("One-time password length", "Lonxitude do contrasinal dun só uso"),
("Request access to your device", "Solicitar acceso ao teu dispositivo"),
("Hide connection management window", "Agochar a ventá de xestión da conexión"),
("hide_cm_tip", "Só se permite agochar se se aceptan sesións mediante contrasinal e se usa contrasinal permanente"),
("wayland_experiment_tip", "A compatibilidade con Wayland está en fase experimental; usa X11 se precisas acceso desatendido."),
("Right click to select tabs", "Clic co botón dereito para seleccionar pestanas"),
("Skipped", "Omitido"),
("Add to address book", "Engadir ao caderno de enderezos"),
("Group", "Grupo"),
("Search", "Buscar"),
("Closed manually by web console", "Pechado manualmente desde a consola web"),
("Local keyboard type", "Tipo de teclado local"),
("Select local keyboard type", "Seleccionar o tipo de teclado local"),
("software_render_tip", "Se usas unha tarxeta gráfica Nvidia en Linux e a ventá remota péchase inmediatamente tras conectar, cambiar ao controlador de código aberto Nouveau e elixir renderizado por software pode axudar. Requírese reiniciar o software."),
("Always use software rendering", "Empregar sempre renderizado por software"),
("config_input", "Para poder controlar o escritorio remoto co teclado, cómpre conceder a RustDesk permisos de «Monitorización de entrada»."),
("config_microphone", "Para poder falar remotamente, cómpre conceder a RustDesk permisos de «Gravar audio»."),
("request_elevation_tip", "Tamén podes solicitar a elevación de privilexios se hai alguén no lado remoto."),
("Wait", "Agardar"),
("Elevation Error", "Erro de elevación"),
("Ask the remote user for authentication", "Pedir autenticación ao usuario remoto"),
("Choose this if the remote account is administrator", "Elixe isto se a conta remota é de administrador"),
("Transmit the username and password of administrator", "Transmitir o nome de usuario e o contrasinal do administrador"),
("still_click_uac_tip", "Aínda require que o usuario remoto prema Aceptar na ventá de UAC de RustDesk en execución."),
("Request Elevation", "Solicitar elevación"),
("wait_accept_uac_tip", "Por favor, agarda a que o usuario remoto acepte o diálogo de UAC."),
("Elevate successfully", "Elevouse correctamente"),
("uppercase", "maiúscula"),
("lowercase", "minúscula"),
("digit", "díxito"),
("special character", "carácter especial"),
("length>=8", "lonxitude>=8"),
("Weak", "Débil"),
("Medium", "Media"),
("Strong", "Forte"),
("Switch Sides", "Intercambiar lados"),
("Please confirm if you want to share your desktop?", "Por favor, confirma se queres compartir o teu escritorio"),
("Display", "Pantalla"),
("Default View Style", "Estilo de visualización predeterminado"),
("Default Scroll Style", "Estilo de desprazamento predeterminado"),
("Default Image Quality", "Calidade de imaxe predeterminada"),
("Default Codec", "Códec predeterminado"),
("Bitrate", "Taxa de bits"),
("FPS", "FPS"),
("Auto", "Automático"),
("Other Default Options", "Outras opcións predeterminadas"),
("Voice call", "Chamada de voz"),
("Text chat", "Conversa de texto"),
("Stop voice call", "Deter chamada de voz"),
("relay_hint_tip", "Quizais non sexa posíbel conectar directamente; podes tentar conectar mediante retransmisión. Ademais, se queres usar a retransmisión no primeiro intento, podes engadir o sufixo «/r» ao ID ou seleccionar a opción «Conectar sempre mediante retransmisión» na tarxeta de sesións recentes se existe."),
("Reconnect", "Reconectar"),
("Codec", "Códec"),
("Resolution", "Resolución"),
("No transfers in progress", "Non hai transferencias en curso"),
("Set one-time password length", "Establecer lonxitude do contrasinal dun só uso"),
("RDP Settings", "Axustes de RDP"),
("Sort by", "Ordenar por"),
("New Connection", "Nova conexión"),
("Restore", "Restaurar"),
("Minimize", "Minimizar"),
("Maximize", "Maximizar"),
("Your Device", "O teu dispositivo"),
("empty_recent_tip", "Vaites, non hai sesións recentes!\nÉ hora de planificar unha nova."),
("empty_favorite_tip", "Aínda non tes pares favoritos?\nBusquemos alguén con quen conectar e engádeo aos teus favoritos!"),
("empty_lan_tip", "Oh non, parece que aínda non descubrimos ningún par."),
("empty_address_book_tip", "Vaites, parece que actualmente non hai pares listados no teu caderno de enderezos."),
("Empty Username", "Nome de usuario baleiro"),
("Empty Password", "Contrasinal baleiro"),
("Me", "Eu"),
("identical_file_tip", "Este ficheiro é idéntico ao do par."),
("show_monitors_tip", "Amosar monitores na barra de ferramentas"),
("View Mode", "Modo de visualización"),
("verify_rustdesk_password_tip", "Verificar o contrasinal de RustDesk"),
("No need to elevate", "Non é necesario elevar"),
("System Sound", "Son do sistema"),
("Default", "Predeterminado"),
("New RDP", "Novo RDP"),
("Fingerprint", "Pegada dixital"),
("Copy Fingerprint", "Copiar pegada dixital"),
("no fingerprints", "Non hai pegadas dixitais"),
("Update", "Actualizar"),
("resolution_original_tip", "Resolución orixinal"),
("resolution_fit_local_tip", "Axustar á resolución local"),
("resolution_custom_tip", "Resolución personalizada"),
("Collapse toolbar", "Pregar a barra de ferramentas"),
("Accept and Elevate", "Aceptar e elevar"),
("accept_and_elevate_btn_tooltip", "Aceptar a conexión e elevar permisos de UAC."),
("clipboard_wait_response_timeout_tip", "Esgotouse o tempo de espera pola resposta de copia."),
("Incoming connection", "Conexión entrante"),
("Outgoing connection", "Conexión saínte"),
("Exit", "Saír"),
("Open", "Abrir"),
("logout_tip", "Tes a certeza de que queres pechar sesión?"),
("Service", "Servizo"),
("Start", "Iniciar"),
("Stop", "Deter"),
("exceed_max_devices", "Acadaches o número máximo de dispositivos xestionados."),
("Sync with recent sessions", "Sincronizar coas sesións recentes"),
("Sort tags", "Ordenar etiquetas"),
("Open connection in new tab", "Abrir conexión nunha nova pestana"),
("Move tab to new window", "Mover a pestana a unha nova ventá"),
("Can not be empty", "Non pode estar baleiro"),
("Already exists", "Xa existe"),
("Change Password", "Cambiar contrasinal"),
("Refresh Password", "Actualizar contrasinal"),
("ID", "ID"),
("Grid View", "Vista en grade"),
("List View", "Vista en lista"),
("Select", "Seleccionar"),
("Toggle Tags", "Alternar etiquetas"),
("pull_ab_failed_tip", "Produciuse un fallo ao actualizar o caderno de enderezos"),
("push_ab_failed_tip", "Produciuse un fallo ao sincronizar o caderno de enderezos co servidor"),
("synced_peer_readded_tip", "Os dispositivos presentes nas sesións recentes sincronizaranse de novo no caderno de enderezos."),
("Change Color", "Cambiar cor"),
("Primary Color", "Cor primaria"),
("HSV Color", "Cor HSV"),
("Installation Successful!", "Instalación correcta!"),
("Installation failed!", "A instalación fallou!"),
("Reverse mouse wheel", "Inverter a roda do rato"),
("{} sessions", "{} sesións"),
("scam_title", "Poderías estar a sufrir unha ESTAFA!"),
("scam_text1", "Se estás ao teléfono con alguén que NON coñeces E no que NON confías que che pediu que uses RustDesk e inicies o servizo, non continúes e colga inmediatamente."),
("scam_text2", "É probábel que sexa un estafador que tenta roubar os teus cartos ou outra información privada."),
("Don't show again", "Non amosar de novo"),
("I Agree", "Estou de acordo"),
("Decline", "Rexeitar"),
("Timeout in minutes", "Tempo límite en minutos"),
("auto_disconnect_option_tip", "Pechar automaticamente as sesións entrantes por inactividade do usuario"),
("Connection failed due to inactivity", "Desconectouse automaticamente por inactividade"),
("Check for software update on startup", "Comprobar se hai actualizacións de software ao arrancar"),
("upgrade_rustdesk_server_pro_to_{}_tip", "Por favor, anova RustDesk Server Pro á versión {} ou máis recente!"),
("pull_group_failed_tip", "Produciuse un fallo ao actualizar o grupo"),
("Filter by intersection", "Filtrar por intersección"),
("Remove wallpaper during incoming sessions", "Retirar o fondo de escritorio durante as sesións entrantes"),
("Test", "Proba"),
("display_is_plugged_out_msg", "Desconectouse a pantalla, cambiando á primeira pantalla."),
("No displays", "Non hai pantallas"),
("Open in new window", "Abrir nunha nova ventá"),
("Show displays as individual windows", "Amosar pantallas como ventás individuais"),
("Use all my displays for the remote session", "Usar todas as miñas pantallas para a sesión remota"),
("selinux_tip", "SELinux está activado no teu dispositivo, o que podería impedir que RustDesk funcione axeitadamente como lado controlado."),
("Change view", "Cambiar vista"),
("Big tiles", "Mosaicos grandes"),
("Small tiles", "Mosaicos pequenos"),
("List", "Lista"),
("Virtual display", "Pantalla virtual"),
("Plug out all", "Desconectar todo"),
("True color (4:4:4)", "Cor verdadeira (4:4:4)"),
("Enable blocking user input", "Activar bloqueo de entrada do usuario"),
("id_input_tip", "Podes introducir un ID, unha IP directa ou un dominio cun porto (<dominio>:<porto>).\nSe queres acceder a un dispositivo noutro servidor, engade o enderezo do servidor (<id>@<enderezo_servidor>?key=<valor_chave>), por exemplo:\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nSe queres acceder a un dispositivo nun servidor público, introduce «<id>@public»; a chave non é precisa para o servidor público.\n\nSe queres forzar o uso dunha conexión por retransmisión no primeiro intento, engade «/r» ao final do ID, por exemplo: «9123456234/r»."),
("privacy_mode_impl_mag_tip", "Modo 1"),
("privacy_mode_impl_virtual_display_tip", "Modo 2"),
("Enter privacy mode", "Entrar en modo de privacidade"),
("Exit privacy mode", "Saír do modo de privacidade"),
("idd_not_support_under_win10_2004_tip", "O controlador de pantalla indirecta non é admitido. Requírese Windows 10, versión 2004 ou posterior."),
("input_source_1_tip", "Fonte de entrada 1"),
("input_source_2_tip", "Fonte de entrada 2"),
("Swap control-command key", "Intercambiar teclas Control e Command"),
("swap-left-right-mouse", "Intercambiar botóns esquerdo e dereito do rato"),
("2FA code", "Código 2FA"),
("More", "Máis"),
("enable-2fa-title", "Activar a autenticación de dous factores"),
("enable-2fa-desc", "Por favor, configura o teu autenticador agora. Podes usar un aplicativo de autenticación como Authy, Microsoft Authenticator ou Google Authenticator no teu teléfono ou computador.\n\nEscanea o código QR co teu aplicativo e introduce o código que este amose para activar a autenticación de dous factores."),
("wrong-2fa-code", "Non se puido verificar o código. Comproba que o código e os axustes da hora local sexan correctos"),
("enter-2fa-title", "Autenticación de dous factores"),
("Email verification code must be 6 characters.", "O código de verificación por correo electrónico debe ter 6 caracteres."),
("2FA code must be 6 digits.", "O código 2FA debe ter 6 díxitos."),
("Multiple Windows sessions found", "Atopáronse múltiples sesións de Windows"),
("Please select the session you want to connect to", "Por favor, selecciona a sesión á que te queres conectar"),
("powered_by_me", "Desenvolvido con RustDesk"),
("outgoing_only_desk_tip", "Esta é unha edición personalizada.\nPodes conectarte a outros dispositivos, mais outros dispositivos non poden conectarse ao teu."),
("preset_password_warning", "Esta edición personalizada inclúe un contrasinal predefinido. Calquera que coñeza este contrasinal poderá obter o control total do teu dispositivo. Se non agardabas isto, desinstala o software de inmediato."),
("Security Alert", "Alerta de seguranza"),
("My address book", "O meu caderno de enderezos"),
("Personal", "Persoal"),
("Owner", "Propietario"),
("Set shared password", "Establecer contrasinal compartido"),
("Exist in", "Existe en"),
("Read-only", "Só lectura"),
("Read/Write", "Lectura/Escrita"),
("Full Control", "Control total"),
("share_warning_tip", "Os campos superiores son compartidos e visíbeis para outros."),
("Everyone", "Todos"),
("ab_web_console_tip", "Máis información na consola web"),
("allow-only-conn-window-open-tip", "Só permitir a conexión se a ventá de RustDesk está aberta"),
("no_need_privacy_mode_no_physical_displays_tip", "Non hai pantallas físicas, non fai falta usar o modo de privacidade."),
("Follow remote cursor", "Seguir o cursor remoto"),
("Follow remote window focus", "Seguir o foco da ventá remota"),
("default_proxy_tip", "O protocolo e porto predeterminados son Socks5 e 1080"),
("no_audio_input_device_tip", "Non se atopou ningún dispositivo de entrada de audio."),
("Incoming", "Entrante"),
("Outgoing", "Saínte"),
("Clear Wayland screen selection", "Limpar selección de pantalla de Wayland"),
("clear_Wayland_screen_selection_tip", "Tras limpar a selección de pantalla, podes seleccionar de novo a pantalla que queres compartir."),
("confirm_clear_Wayland_screen_selection_tip", "Tes a certeza de que queres limpar a selección de pantalla de Wayland?"),
("android_new_voice_call_tip", "Recibiuse unha nova solicitude de chamada de voz. Se aceptas, o audio cambiará a comunicación por voz."),
("texture_render_tip", "Empregar a renderización de texturas para facer as imaxes máis suaves. Podes tentar desactivar esta opción se atopas problemas de renderización."),
("Use texture rendering", "Usar renderización de texturas"),
("Floating window", "Ventá flotante"),
("floating_window_tip", "Axuda a manter o servizo de RustDesk en segundo plano"),
("Keep screen on", "Manter a pantalla acesa"),
("Never", "Nunca"),
("During controlled", "Mentres está controlado"),
("During service is on", "Mentres o servizo estea activo"),
("Capture screen using DirectX", "Capturar pantalla usando DirectX"),
("Back", "Atrás"),
("Apps", "Aplicativos"),
("Volume up", "Subir volume"),
("Volume down", "Baixar volume"),
("Power", "Enerxía"),
("Telegram bot", "Bot de Telegram"),
("enable-bot-tip", "Se activas esta función, poderás recibir o código 2FA desde o teu bot. Tamén pode funcionar como notificación de conexión."),
("enable-bot-desc", "1. Abre unha conversa con @BotFather.\n2. Envía a orde «/newbot». Recibirás un token tras completar este paso.\n3. Inicia unha conversa co teu bot acabado de crear. Envía unha mensaxe que comece cunha barra inclinada («/») como «/hello» para activalo.\n"),
("cancel-2fa-confirm-tip", "Tes a certeza de que queres cancelar o 2FA?"),
("cancel-bot-confirm-tip", "Tes a certeza de que queres cancelar o bot de Telegram?"),
("About RustDesk", "Sobre RustDesk"),
("Send clipboard keystrokes", "Enviar pulsacións de teclas do portapapeis"),
("network_error_tip", "Por favor, comproba a túa conexión de rede e despois preme en tentar de novo."),
("Unlock with PIN", "Desbloquear con PIN"),
("Requires at least {} characters", "Require polo menos {} caracteres"),
("Wrong PIN", "PIN incorrecto"),
("Set PIN", "Establecer PIN"),
("Enable trusted devices", "Activar dispositivos de confianza"),
("Manage trusted devices", "Xestionar dispositivos de confianza"),
("Platform", "Plataforma"),
("Days remaining", "Días restantes"),
("enable-trusted-devices-tip", "Omitir a verificación 2FA en dispositivos de confianza"),
("Parent directory", "Directorio pai"),
("Resume", "Continuar"),
("Invalid file name", "Nome de ficheiro non válido"),
("one-way-file-transfer-tip", "A transferencia unidireccional de ficheiros está activada no lado controlado."),
("Authentication Required", "Requírese autenticación"),
("Authenticate", "Autenticar"),
("web_id_input_tip", "Podes introducir un ID no mesmo servidor; o acceso directo por IP non é admitido no cliente web.\nSe queres acceder a un dispositivo noutro servidor, engade o enderezo do servidor (<id>@<enderezo_servidor>?key=<valor_chave>), por exemplo:\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nSe queres acceder a un dispositivo nun servidor público, introduce «<id>@public»; a chave non é precisa para o servidor público."),
("Download", "Descargar"),
("Upload folder", "Subir cartafol"),
("Upload files", "Subir ficheiros"),
("Clipboard is synchronized", "O portapapeis está sincronizado"),
("Update client clipboard", "Actualizar o portapapeis do cliente"),
("Untagged", "Sen etiquetar"),
("new-version-of-{}-tip", "Hai unha nova versión dispoñíbel de {}"),
("Accessible devices", "Dispositivos accesíbeis"),
("upgrade_remote_rustdesk_client_to_{}_tip", "Por favor, anova o cliente de RustDesk á versión {} ou máis recente no lado remoto!"),
("d3d_render_tip", "Cando se activa a renderización D3D, a pantalla de control remoto pode quedar en negro nalgúns equipos."),
("Use D3D rendering", "Usar renderización D3D"),
("Printer", "Impresora"),
("printer-os-requirement-tip", "A función de saída de impresora require Windows 10 ou superior."),
("printer-requires-installed-{}-client-tip", "Para usar a impresión remota, cómpre instalar {} neste dispositivo."),
("printer-{}-not-installed-tip", "A impresora {} non está instalada."),
("printer-{}-ready-tip", "A impresora {} está instalada e lista para usar."),
("Install {} Printer", "Instalar a impresora {}"),
("Outgoing Print Jobs", "Traballos de impresión saíntes"),
("Incoming Print Jobs", "Traballos de impresión entrantes"),
("Incoming Print Job", "Traballo de impresión entrante"),
("use-the-default-printer-tip", "Usar a impresora predeterminada"),
("use-the-selected-printer-tip", "Usar a impresora seleccionada"),
("auto-print-tip", "Imprimir automaticamente usando a impresora seleccionada."),
("print-incoming-job-confirm-tip", "Recibiches un traballo de impresión desde o equipo remoto. Queres executalo no teu equipo?"),
("remote-printing-disallowed-tile-tip", "Impresión remota non permitida"),
("remote-printing-disallowed-text-tip", "Os axustes de permisos do lado controlado denegan a impresión remota."),
("save-settings-tip", "Gardar axustes"),
("dont-show-again-tip", "Non amosar isto de novo"),
("Take screenshot", "Facer captura de pantalla"),
("Taking screenshot", "Facendo captura de pantalla"),
("screenshot-merged-screen-not-supported-tip", "A combinación de capturas de pantalla de múltiples pantallas non é admitida actualmente. Por favor, cambia a unha soa pantalla e téntao de novo."),
("screenshot-action-tip", "Por favor, selecciona como continuar coa captura de pantalla."),
("Save as", "Gardar como"),
("Export", "Exportar"),
("Export Logs", "Exportar rexistros"),
("Import Folder", "Importar cartafol"),
("Copy to clipboard", "Copiar no portapapeis"),
("Enable remote printer", "Activar impresora remota"),
("Downloading {}", "Descargando {}"),
("{} Update", "Actualización de {}"),
("{}-to-update-tip", "{} pecharase agora e instalará a nova versión."),
("download-new-version-failed-tip", "Produciuse un fallo na descarga. Podes tentalo de novo ou premer o botón «Descargar» para descargar desde a páxina de lanzamentos e anovar manualmente."),
("Auto update", "Actualización automática"),
("update-failed-check-msi-tip", "Produciuse un fallo na comprobación do método de instalación. Por favor, preme o botón «Descargar» para descargar desde a páxina de lanzamentos e anovar manualmente."),
("websocket_tip", "Ao usar WebSocket, só se admiten conexións por retransmisión."),
("Use WebSocket", "Usar WebSocket"),
("Trackpad speed", "Velocidade do panel táctil"),
("Default trackpad speed", "Velocidade predeterminada do panel táctil"),
("Numeric one-time password", "Contrasinal numérico dun só uso"),
("Enable IPv6 P2P connection", "Activar conexión P2P por IPv6"),
("Enable UDP hole punching", "Activar perforación de portos UDP"),
("View camera", "Ver cámara"),
("Enable camera", "Activar cámara"),
("No cameras", "Non hai cámaras"),
("view_camera_unsupported_tip", "O dispositivo remoto non admite ver a cámara."),
("Terminal", "Terminal"),
("Enable terminal", "Activar terminal"),
("New tab", "Nova pestana"),
("Keep terminal sessions on disconnect", "Manter as sesións de terminal ao desconectar"),
("Terminal (Run as administrator)", "Terminal (executar como administrador)"),
("terminal-admin-login-tip", "Por favor, introduce o nome de usuario e contrasinal de administrador do lado controlado."),
("Failed to get user token.", "Produciuse un fallo ao obter o token de usuario."),
("Incorrect username or password.", "Nome de usuario ou contrasinal incorrectos."),
("The user is not an administrator.", "O usuario non é administrador."),
("Failed to check if the user is an administrator.", "Produciuse un fallo ao comprobar se o usuario é administrador."),
("Supported only in the installed version.", "Só é admitido na versión instalada."),
("elevation_username_tip", "Introduce nome de usuario ou dominio\\usuario"),
("Preparing for installation ...", "Preparando para a instalación..."),
("Show my cursor", "Amosar o meu cursor"),
("Scale custom", "Escala personalizada"),
("Custom scale slider", "Control desprazábel de escala personalizada"),
("Decrease", "Diminuír"),
("Increase", "Aumentar"),
("Show virtual mouse", "Amosar rato virtual"),
("Virtual mouse size", "Tamaño do rato virtual"),
("Small", "Pequeno"),
("Large", "Grande"),
("Show virtual joystick", "Amosar mando virtual"),
("Edit note", "Editar nota"),
("Alias", "Alias"),
("ScrollEdge", "Bordo de desprazamento"),
("Allow insecure TLS fallback", "Permitir retroceso inseguro a TLS"),
("allow-insecure-tls-fallback-tip", "De maneira predeterminada, RustDesk verifica o certificado do servidor para os protocolos que usan TLS.\nCon esta opción activada, RustDesk omitirá o paso de verificación e continuará en caso de fallo de verificación."),
("Disable UDP", "Desactivar UDP"),
("disable-udp-tip", "Controla se usar só TCP.\nCando esta opción estea activada, RustDesk xa non usará o porto UDP 21116; no seu lugar usarase o porto TCP 21116."),
("server-oss-not-support-tip", "NOTA: O servidor de código aberto (OSS) de RustDesk non inclúe esta funcionalidade."),
("input note here", "escribe a nota aquí"),
("note-at-conn-end-tip", "Pedir unha nota ao rematar a conexión"),
("Show terminal extra keys", "Amosar teclas adicionais do terminal"),
("Relative mouse mode", "Modo de rato relativo"),
("rel-mouse-not-supported-peer-tip", "O modo de rato relativo non é admitido polo par conectado."),
("rel-mouse-not-ready-tip", "O modo de rato relativo aínda non está listo. Por favor, téntao de novo."),
("rel-mouse-lock-failed-tip", "Produciuse un fallo ao bloquear o cursor. Desactivouse o modo de rato relativo."),
("rel-mouse-exit-{}-tip", "Preme {} para saír."),
("rel-mouse-permission-lost-tip", "Revogouse o permiso de teclado. Desactivouse o modo de rato relativo."),
("Changelog", "Rexistro de cambios"),
("keep-awake-during-outgoing-sessions-label", "Manter a pantalla acesa durante as sesións saíntes"),
("keep-awake-during-incoming-sessions-label", "Manter a pantalla acesa durante as sesións entrantes"),
("Continue with {}", "Continuar con {}"),
("Display Name", "Nome para amosar"),
("password-hidden-tip", "O contrasinal permanente está configurado (agochado)."),
("preset-password-in-use-tip", "O contrasinal predefinido está actualmente en uso."),
("Enable privacy mode", "Activar modo de privacidade"),
("allow-remote-toolbar-docking-any-edge", "Permitir ancorar a barra de ferramentas remota en calquera bordo da ventá"),
("API Token", "Token da API"),
("Deploy", "Despregar"),
("Custom ID (optional)", "ID personalizado (opcional)"),
("server_requires_deployment_tip", "O servidor require que este dispositivo sexa despregado explicitamente. Despregar agora?"),
("The server does not require explicit deployment.", "O servidor non require despregamento explícito."),
("Unknown response.", "Resposta descoñecida."),
("wayland-keyboard-input-disabled-tip", "Permitir entrada de teclado?"),
("wayland-keyboard-input-consent-tip", "O que escribas neste computador remoto (incluídos os contrasinais) podería ser lido por outros aplicativos nel."),
("wayland-keyboard-input-applies-to-tip", "Esta opción aplícase a:"),
("wayland-soft-keyboard-input-label", "Entrada de teclado en pantalla"),
("wayland-keyboard-input-reset-choice-tip", "Restablecer opción de entrada de teclado"),
("remember-wayland-keyboard-choice-tip", "Non preguntar de novo para este computador remoto"),
("Why this happens", "Por que acontece isto?"),
("Switch display", "Cambiar de pantalla"),
("Show monitor switch button on the main toolbar", "Amosar o botón de cambio de monitor na barra de ferramentas principal"),
("Show on the minimized toolbar", "Amosar na barra de ferramentas minimizada"),
("All monitors", "Todos os monitores"),
("#{} monitor", "Monitor #{}"),
("conn-e2ee-unavailable-tip", "Non se puido verificar o cifrado de extremo a extremo.\nO dispositivo remoto aínda se pode estar a configurar. Téntao máis tarde.\nSe isto segue a ocorrer, é posíbel que o servidor non sexa de confianza.\nQueres continuar de todos os xeitos?"),
("ID whitelisting", "Lista branca de ID"),
("Use ID whitelisting", "Usar lista branca de ID"),
("id_whitelist_tip", "Só os ID da lista branca poden acceder a min"),
("id_whitelist_wildcard_tip", "Admítense caracteres comodín: '*' coincide con calquera número de caracteres, '?' coincide exactamente cun carácter"),
("Invalid ID", "ID non válido"),
("Your ID is blocked by the peer", "O teu ID está bloqueado polo par"),
("Your ip is blocked by the peer", "A túa IP está bloqueada polo par"),
("id_whitelist_caveat_tip", "O ID é comunicado polo cliente que se conecta. Esta lista branca reduce a exposición e non substitúe o contrasinal nin o 2FA."),
("whitelist_cidr_tip", "Admítese a notación CIDR, por exemplo: 192.168.1.0/24"),
("Continue", "Continuar"),
("Browser didn't open? Use the url below to sign in.", "Non se abriu o navegador? Usa o URL de abaixo para iniciar sesión."),
("Lock canvas", "Bloquear lenzo"),
("Sync clipboard between sessions", "Sincronizar o portapapeis entre sesións"),
("sync-clipboard-between-sessions-tip", "O texto ou as imaxes copiadas nunha sesión remota tamén se envían ao portapapeis das túas outras sesións conectadas."),
("terminal-clipboard-write-tip", "Un aplicativo no terminal quere copiar texto no portapapeis deste dispositivo. Se se concede, este permiso aplicarase aos aplicativos de terminal en todas as conexións ata que o desactives en Axustes. O copiar e pegar manual non se ven afectados."),
("Allow terminal apps to copy to clipboard", "Permitir que os aplicativos de terminal copien no portapapeis"),
("Enable", "Activar"),
("Reuse one connection for port forwarding", "Reutilizar unha conexión para o reenvío de portos"),
("port-forward-mux-tip", "Canalizar todas as conexións dun mapeo de reenvío de portos a través dunha única conexión co par, en lugar de conectar e iniciar sesión de novo para cada unha."),
("Enable WebRTC P2P connection", "Activar conexión P2P por WebRTC"),
("Enable TCP hole punching", "Activar perforación de portos TCP"),
].iter().cloned().collect();
}

View File

@@ -660,7 +660,7 @@ pub static ref T: std::collections::HashMap<&'static str, &'static str> =
("screenshot-action-tip", "Seleziona come continuare con la schermata."),
("Save as", "Salva come"),
("Export", "Esporta"),
("Export Logs", "Esporta i log"),
("Export Logs", "Esporta registri"),
("Import Folder", "Importa cartella"),
("Copy to clipboard", "Copia negli appunti"),
("Enable remote printer", "Abilita stampante remota"),
@@ -761,13 +761,13 @@ pub static ref T: std::collections::HashMap<&'static str, &'static str> =
("Continue", "Continua"),
("Browser didn't open? Use the url below to sign in.", "Il browser non si è aperto? Usa l'URL qui sotto per accedere."),
("Lock canvas", "Blocca tela"),
("Sync clipboard between sessions", "Sincronizza gli appunti tra le sessioni"),
("Sync clipboard between sessions", "Sincronizza appunti tra le sessioni"),
("sync-clipboard-between-sessions-tip", "Il testo o le immagini copiati in una sessione remota vengono inviati anche agli appunti delle altre sessioni connesse."),
("terminal-clipboard-write-tip", ""),
("Allow terminal apps to copy to clipboard", ""),
("terminal-clipboard-write-tip", "Un'app nel terminale vuole copiare il testo negli appunti di questo dispositivo. Se concessa, questa autorizzazione si applica alle app terminali in tutte le connessioni finché non la disattivi in Impostazioni. Le operazioni di copia e incolla manuali non sono interessate."),
("Allow terminal apps to copy to clipboard", "Consenti alle app terminali di copiare negli appunti"),
("Enable", "Abilita"),
("Reuse one connection for port forwarding", "Riutilizza una sola connessione per l'inoltro delle porte"),
("port-forward-mux-tip", "Fa passare tutte le connessioni di un inoltro di porte su un'unica connessione verso il dispositivo remoto, invece di connettersi e autenticarsi di nuovo per ognuna."),
("Reuse one connection for port forwarding", "Per l'inoltro delle porte riusa una sola connessione "),
("port-forward-mux-tip", "Fa passare tutte le connessioni di un inoltro porte in un'unica connessione verso il dispositivo remoto, invece di connettersi e autenticarsi di nuovo per ognuna."),
("Enable WebRTC P2P connection", "Abilita connessione P2P WebRTC"),
("Enable TCP hole punching", "Abilita hole punching TCP"),
].iter().cloned().collect();