Files
rustdesk/src/lang/hr.rs
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

775 lines
50 KiB
Rust

lazy_static::lazy_static! {
pub static ref T: std::collections::HashMap<&'static str, &'static str> =
[
("Status", "Status"),
("Your Desktop", "Vaša radna površina"),
("desk_tip", "Vašoj radnoj površini se može pristupiti ovim ID i lozinkom."),
("Password", "Lozinka"),
("Ready", "Spremno"),
("Established", "Uspostavljeno"),
("connecting_status", "Spajanje na RustDesk mrežu..."),
("Enable service", "Dopusti servis"),
("Start service", "Pokreni servis"),
("Service is running", "Servis je pokrenut"),
("Service is not running", "Servis nije pokrenut"),
("not_ready_status", "Nije spremno. Provjerite vezu."),
("Control Remote Desktop", "Upravljanje udaljenom radnom površinom"),
("Transfer file", "Prijenos datoteke"),
("Connect", "Spajanje"),
("Recent sessions", "Nedavne sesije"),
("Address book", "Adresar"),
("Confirmation", "Potvrda"),
("TCP tunneling", "TCP tunel"),
("Remove", "Ukloni"),
("Refresh random password", "Osvježi slučajnu lozinku"),
("Set your own password", "Postavi lozinku"),
("Enable keyboard/mouse", "Dopusti tipkovnicu/miša"),
("Enable clipboard", "Dopusti međuspremnik"),
("Enable file transfer", "Dopusti prijenos datoteka"),
("Enable TCP tunneling", "Dopusti TCP tunel"),
("IP Whitelisting", "IP pouzdana lista"),
("ID/Relay Server", "ID/Posredni poslužitelj"),
("Import server config", "Uvoz konfiguracije poslužitelja"),
("Export Server Config", "Izvoz konfiguracije poslužitelja"),
("Import server configuration successfully", "Uvoz konfiguracije poslužitelja uspješan"),
("Export server configuration successfully", "Izvoz konfiguracije poslužitelja uspješan"),
("Invalid server configuration", "Pogrešna konfiguracija poslužitelja"),
("Clipboard is empty", "Međuspremnik je prazan"),
("Stop service", "Zaustavi servis"),
("Change ID", "Promijeni ID"),
("Your new ID", "Vaš novi ID"),
("length %min% to %max%", "duljina %min% do %max%"),
("starts with a letter", "Počinje slovom"),
("allowed characters", "Dopušteni znakovi"),
("id_change_tip", "Dopušteni su samo a-z, A-Z, 0-9, - (dash) i _ (donja crta) znakovi. Prvi znak mora biti slovo a-z, A-Z. Duljina je od 6 do 16."),
("Website", "Web stranica"),
("About", "O programu"),
("Slogan_tip", "Stvoren srcem u ovom kaotičnom svijetu!"),
("Privacy Statement", "Izjava o privatnosti"),
("Mute", "Utišaj"),
("Build Date", "Datum izrade"),
("Version", "Verzija"),
("Home", "Početno"),
("Audio Input", "Audio ulaz"),
("Enhancements", "Proširenja"),
("Hardware Codec", "Hardverski kodek"),
("Adaptive bitrate", "Prilagodljiva gustoća podataka"),
("ID Server", "ID poslužitelja"),
("Relay Server", "Posredni poslužitelj"),
("API Server", "API poslužitelj"),
("invalid_http", "Treba početi sa http:// ili https://"),
("Invalid IP", "Nevažeća IP"),
("Invalid format", "Pogrešan format"),
("server_not_support", "Poslužitelj još uvijek ne podržava"),
("Not available", "Nije dostupno"),
("Too frequent", "Previše često"),
("Cancel", "Otkaži"),
("Skip", "Preskoči"),
("Close", "Zatvori"),
("Retry", "Ponovi"),
("OK", "Ok"),
("Password Required", "Potrebna lozinka"),
("Please enter your password", "Molimo unesite svoju lozinku"),
("Remember password", "Zapamti lozinku"),
("Wrong Password", "Pogrešna lozinka"),
("Do you want to enter again?", "Želite li ponovo unijeti lozinku?"),
("Connection Error", "Greška u spajanju"),
("Error", "Greška"),
("Reset by the peer", "Prekinuto sa druge strane"),
("Connecting...", "Povezivanje..."),
("Connection in progress. Please wait.", "Povezivanje u tijeku. Molimo pričekajte."),
("Please try 1 minute later", "Pokušajte minutu kasnije"),
("Login Error", "Greška kod prijave"),
("Successful", "Uspješno"),
("Connected, waiting for image...", "Spojeno, pričekajte sliku..."),
("Name", "Ime"),
("Type", "Vrsta"),
("Modified", "Izmijenjeno"),
("Size", "Veličina"),
("Show Hidden Files", "Prikaži skrivene datoteke"),
("Receive", "Prijem"),
("Send", "Slanje"),
("Refresh File", "Osvježi datoteku"),
("Local", "Lokalno"),
("Remote", "Udaljeno"),
("Remote Computer", "Udaljeno računalo"),
("Local Computer", "Lokalno računalo"),
("Confirm Delete", "Potvrdite brisanje"),
("Delete", "Brisanje"),
("Properties", "Svojstva"),
("Multi Select", "Višestruki odabir"),
("Select All", "Odaberi sve"),
("Unselect All", "Poništi odabir"),
("Empty Directory", "Prazna mapa"),
("Not an empty directory", "Nije prazna mapa"),
("Are you sure you want to delete this file?", "Jeste sigurni da želite obrisati ovu datoteku?"),
("Are you sure you want to delete this empty directory?", "Jeste sigurni da želite obrisati ovu praznu mapu?"),
("Are you sure you want to delete the file of this directory?", "Jeste sigurni da želite obrisati datoteku u ovoj mapi?"),
("Do this for all conflicts", "Učinite to za sve sukobe"),
("This is irreversible!", "Ovo je nepovratno"),
("Deleting", "Brisanje"),
("files", "datoteke"),
("Waiting", "Čekanje"),
("Finished", "Završeno"),
("Speed", "Brzina"),
("Custom Image Quality", "Korisnička kvaliteta slike"),
("Privacy mode", "Način privatnosti"),
("Block user input", "Blokiraj korisnikov unos"),
("Unblock user input", "Odblokiraj korisnikov unos"),
("Adjust Window", "Podesi prozor"),
("Original", "Izvornik"),
("Shrink", "Skupi"),
("Stretch", "Raširi"),
("Scrollbar", "Linija pomaka"),
("ScrollAuto", "Autom. pomak"),
("Good image quality", "Dobra kvaliteta slike"),
("Balanced", "Balansirano"),
("Optimize reaction time", "Optimizirano vrijeme reakcije"),
("Custom", "Korisničko"),
("Show remote cursor", "Prikaži udaljeni kursor"),
("Show quality monitor", "Prikaži kvalitetu monitora"),
("Disable clipboard", "Zabrani međuspremnik"),
("Lock after session end", "Zaključaj po završetku sesije"),
("Insert Ctrl + Alt + Del", "Ctrl + Alt + Del umetanje"),
("Insert Lock", "Zaključaj umetanje"),
("Refresh", "Osvježi"),
("ID does not exist", "ID ne postoji"),
("Failed to connect to rendezvous server", "Greška u spajanju na poslužitelj za povezivanje"),
("Please try later", "Molimo pokušajte kasnije"),
("Remote desktop is offline", "Udaljeni zaslon je isključen"),
("Key mismatch", "Pogrešan ključ"),
("Timeout", "Isteklo vrijeme"),
("Failed to connect to relay server", "Greška u spajanju na posredni poslužitelj"),
("Failed to connect via rendezvous server", "Greška u spajanju preko poslužitelja za povezivanje"),
("Failed to connect via relay server", "Greška u spajanju preko posrednog poslužitelja"),
("Failed to make direct connection to remote desktop", "Greška u direktnom spajanju na udaljenu radnu površinu"),
("Set Password", "Postavi lozinku"),
("OS Password", "Lozinka OS-a"),
("install_tip", "Zbog UAC-a RustDesk ne može u nekim slučajevima raditi pravilno. Da biste prevazišli UAC, kliknite na tipku ispod da instalirate RustDesk na sustav."),
("Click to upgrade", "Klik za nadogradnju"),
("Configure", "Konfiguracija"),
("config_acc", "Da biste daljinski kontrolirali radnu površinu, RustDesk-u trebate dodijeliti prava za \"Pristupačnost\"."),
("config_screen", "Da biste daljinski pristupili radnoj površini, RustDesk-u trebate dodijeliti prava za \"Snimanje zaslona\"."),
("Installing ...", "Instaliranje..."),
("Install", "Instaliraj"),
("Installation", "Instalacija"),
("Installation Path", "Putanja za instalaciju"),
("Create start menu shortcuts", "Stvori prečace u izborniku"),
("Create desktop icon", "Stvori ikonu na radnoj površini"),
("agreement_tip", "Pokretanjem instalacije prihvaćate ugovor o licenciranju."),
("Accept and Install", "Prihvati i instaliraj"),
("End-user license agreement", "Ugovor sa krajnjim korisnikom"),
("Generating ...", "Generiranje..."),
("Your installation is lower version.", "Vaša instalacija je niže verzije"),
("not_close_tcp_tip", "Ne zatvarajte ovaj prozor dok koristite tunel"),
("Listening ...", "Na slušanju..."),
("Remote Host", "Adresa udaljenog uređaja"),
("Remote Port", "Udaljeni port"),
("Action", "Postupak"),
("Add", "Dodaj"),
("Local Port", "Lokalni port"),
("Local Address", "Lokalna adresa"),
("Change Local Port", "Promijeni lokalni port"),
("setup_server_tip", "Za brže spajanje, molimo da koristite vlastiti poslužitelj"),
("Too short, at least 6 characters.", "Prekratko, najmanje 6 znakova."),
("The confirmation is not identical.", "Potvrda nije identična"),
("Permissions", "Dopuštenja"),
("Accept", "Prihvati"),
("Dismiss", "Odbaci"),
("Disconnect", "Prekini vezu"),
("Enable file copy and paste", "Dopusti kopiranje i lijepljenje datoteka"),
("Connected", "Spojeno"),
("Direct and encrypted connection", "Izravna i kriptirana veza"),
("Relayed and encrypted connection", "Posredna i kriptirana veza"),
("Direct and unencrypted connection", "Izravna i nekriptirana veza"),
("Relayed and unencrypted connection", "Posredna i nekriptirana veza"),
("Enter Remote ID", "Unesite ID udaljenog uređaja"),
("Enter your password", "Unesite svoju lozinku"),
("Logging in...", "Prijava..."),
("Enable RDP session sharing", "Dopusti dijeljenje RDP sesije"),
("Auto Login", "Autom. prijava (Vrijedi samo ako je postavljeno \"Zaključavanje nakon završetka sesije\")"),
("Enable direct IP access", "Dopusti izravan pristup preko IP adrese"),
("Rename", "Preimenuj"),
("Space", "Prazno"),
("Create desktop shortcut", "Stvori prečac na radnoj površini"),
("Change Path", "Promijeni putanju"),
("Create Folder", "Svori mapu"),
("Please enter the folder name", "Unesite ime mape"),
("Fix it", "Popravi"),
("Warning", "Upozorenje"),
("Login screen using Wayland is not supported", "Zaslon za prijavu koji koristi Wayland nije podržan"),
("Reboot required", "Potrebano je ponovno pokretanje"),
("Unsupported display server", "Nepodržani poslužitelj za prikaz"),
("x11 expected", "x11 očekivan"),
("Port", "Port"),
("Settings", "Postavke"),
("Username", "Korisničko ime"),
("Invalid port", "Pogrešan port"),
("Closed manually by the peer", "Klijent ručno prekinuo vezu"),
("Enable remote configuration modification", "Dopusti izmjenu udaljene konfiguracije"),
("Run without install", "Pokreni bez instalacije"),
("Connect via relay", "Povezivanje preko relejnog poslužitelja"),
("Always connect via relay", "Uvek se poveži preko relejnog poslužitelja"),
("whitelist_tip", "Mogu mi pristupiti samo dozvoljene IP adrese"),
("Login", "Prijava"),
("Verify", "Potvrdi"),
("Remember me", "Zapamti me"),
("Trust this device", "Vjeruj ovom uređaju"),
("Verification code", "Kontrolni kôd"),
("verification_tip", "Kontrolni kôd je poslan na registriranu adresu e-pošte, unesite ga i nastavite s prijavom."),
("Logout", "Odjava"),
("Tags", "Oznake"),
("Search ID", "Traži ID"),
("whitelist_sep", "Odvojeno zarezima, točka zarezima, praznim mjestima ili novim redovima"),
("Add ID", "Dodaj ID"),
("Add Tag", "Dodaj oznaku"),
("Unselect all tags", "Odznači sve oznake"),
("Network error", "Greška na mreži"),
("Username missed", "Korisničko ime propušteno"),
("Password missed", "Lozinka propuštena"),
("Wrong credentials", "Pogrešno korisničko ime ili lozinka"),
("The verification code is incorrect or has expired", "Kôd za provjeru nije točan ili je istekao"),
("Edit Tag", "Izmjenite oznaku"),
("Forget Password", "Zaboravi lozinku"),
("Favorites", "Favoriti"),
("Add to Favorites", "Dodaj u favorite"),
("Remove from Favorites", "Ukloni iz favorita"),
("Empty", "Prazno"),
("Invalid folder name", "Nevažeći naziv mape"),
("Socks5 Proxy", "Socks5 Proxy"),
("Socks5/Http(s) Proxy", "Socks5/Http(s) proxy"),
("Discovered", "Otkriveno"),
("install_daemon_tip", "Servis sustava mora biti instaliran ako se želi pokrenuti pri pokretanju sustava."),
("Remote ID", "Udaljeni ID"),
("Paste", "Zalijepi"),
("Paste here?", "Zalijepi ovdje?"),
("Are you sure to close the connection?", "Jeste li sigurni da želite zatvoriti vezu?"),
("Download new version", "Preuzmi novu verziju"),
("Touch mode", "Način rada na dodir"),
("Mouse mode", "Način rada miša"),
("One-Finger Tap", "Dodir jednim prstom"),
("Left Mouse", "Lijeva tipka miša"),
("One-Long Tap", "Jedan dugi dodir"),
("Two-Finger Tap", "Dodir s dva prsta"),
("Right Mouse", "Desna tipka miša"),
("One-Finger Move", "Pomak jednim prstom"),
("Double Tap & Move", "Dupli dodir i pomak"),
("Mouse Drag", "Povlačenje mišem"),
("Three-Finger vertically", "Sa tri prsta okomito"),
("Mouse Wheel", "Kotačić miša"),
("Two-Finger Move", "Pomak s dva prsta"),
("Canvas Move", "Pomak pozadine"),
("Pinch to Zoom", "Stisnite prste za zumiranje"),
("Canvas Zoom", "Zumiranje pozadine"),
("Reset canvas", "Resetiraj pozadinu"),
("No permission of file transfer", "Nemate pravo prijenosa datoteka"),
("Note", "Bilješka"),
("Connection", "Povezivanje"),
("Share screen", "Podijeli zaslon"),
("Chat", "Dopisivanje"),
("Total", "Ukupno"),
("items", "stavki"),
("Selected", "Odabrano"),
("Screen Capture", "Snimanje zaslona"),
("Input Control", "Kontrola unosa"),
("Audio Capture", "Snimanje zvuka"),
("Do you accept?", "Prihvaćate li?"),
("Open System Setting", "Postavke otvorenog sustava"),
("How to get Android input permission?", "Kako dobiti pristup za unos na Androidu?"),
("android_input_permission_tip1", "Da bi ste daljinski uređaj kontrolirali vašim Android uređajem preko miša ili na dodir, trebate dopustiti RustDesk-u da koristi servis \"Pristupačnost\"."),
("android_input_permission_tip2", "Molimo prijeđite na sljedeću stranicu podešavanja sustava, pronađite i unesite [Instalirani servisi], uključite servis [RustDesk Input]."),
("android_new_connection_tip", "Primljen je novi zahtjev za upravljanje, koji želi upravljati vašim uređajem."),
("android_service_will_start_tip", "Omogućavanje \"Snimanje zaslona\" automatski će pokrenuti servis, dopuštajući drugim uređajima da zahtjevaju spajanje na vaš uređaj."),
("android_stop_service_tip", "Zatvaranje servisa automatski će zatvoriti sve uspostavljene veze."),
("android_version_audio_tip", "Trenutna Android verzija ne podržava audio snimanje, molimo nadogradite na Android 10 ili veći."),
("android_start_service_tip", "Pritisnite [Pokreni servis] ili omogućite dopuštenje [Snimanje zaslona] za pokretanje usluge dijeljenja zaslona."),
("android_permission_may_not_change_tip", "Dopuštenja za uspostavljene veze mogu se promijeniti tek nakon ponovnog povezivanja."),
("Account", "Račun"),
("Overwrite", "Prepiši"),
("This file exists, skip or overwrite this file?", "Ova datoteka postoji, preskoči ju ili prepiši?"),
("Quit", "Izlaz"),
("Help", "Pomoć"),
("Failed", "Neuspješno"),
("Succeeded", "Uspešno"),
("Someone turns on privacy mode, exit", "Netko je uključio način privatnosti, izlaz."),
("Unsupported", "Nepodržano"),
("Peer denied", "Klijent zabranjen"),
("Peer exit", "Klijent je izašao"),
("Failed to turn off", "Greška kod isključenja"),
("Turned off", "Isključeno"),
("Language", "Jezik"),
("Keep RustDesk background service", "Zadrži RustDesk kao pozadinski servis"),
("Ignore Battery Optimizations", "Zanemari optimizaciju baterije"),
("android_open_battery_optimizations_tip", "Ako želite onemogućiti ovu funkciju, molimo idite na sljedeću stranicu za podešavanje RustDesk aplikacije, pronađite i uđite u [Baterija], onemogućite [Neograničeno]"),
("Start on boot", "Pokreni pri pokretanju sustava"),
("Start the screen sharing service on boot, requires special permissions", "Za pokretanje usluge dijeljenja zaslona pri pokretanju sustava potrebna su posebna dopuštenja"),
("Connection not allowed", "Veza nije dopuštena"),
("Legacy mode", "Naslijeđeni način"),
("Map mode", "Način mapiranja"),
("Translate mode", "Način prevođenja"),
("Use permanent password", "Koristi trajnu lozinku"),
("Use both passwords", "Koristi obje lozinke"),
("Set permanent password", "Postavi trajnu lozinku"),
("Enable remote restart", "Omogući daljinsko ponovno pokretanje"),
("Restart remote device", "Ponovno pokreni daljinski uređaj"),
("Are you sure you want to restart", "Jeste li sigurni da želite ponovno pokretanje"),
("Restarting remote device", "Ponovno pokretanje daljinskog uređaja"),
("remote_restarting_tip", "Udaljeni uređaj se ponovno pokreće, molimo zatvorite ovu poruku i ponovo se kasnije povežite trajnom lozinkom"),
("Copied", "Kopirano"),
("Exit Fullscreen", "Izlaz iz cijelog zaslona"),
("Fullscreen", "Cijeli zaslon"),
("Mobile Actions", "Mobilne akcije"),
("Select Monitor", "Odabir monitora"),
("Control Actions", "Kontrolni postupci"),
("Display Settings", "Postavke prikaza"),
("Ratio", "Odnos"),
("Image Quality", "Kvaliteta slike"),
("Scroll Style", "Način pomaka"),
("Show Toolbar", "Prikaži alatnu traku"),
("Hide Toolbar", "Sakrij alatnu traku"),
("Direct Connection", "Izravna veza"),
("Relay Connection", "Posredna veza"),
("Secure Connection", "Sigurna veza"),
("Insecure Connection", "Nesigurna veza"),
("Scale original", "Skaliraj izvornik"),
("Scale adaptive", "Prilagođeno skaliranje"),
("General", "Općenito"),
("Security", "Sigurnost"),
("Theme", "Tema"),
("Dark Theme", "Tamna tema"),
("Light Theme", "Svjetla tema"),
("Dark", "Tamna"),
("Light", "Svjetla"),
("Follow System", "Tema sutava"),
("Enable hardware codec", "Omogući hardverski kodek"),
("Unlock Security Settings", "Otključaj postavke sigurnosti"),
("Enable audio", "Dopusti zvuk"),
("Unlock Network Settings", "Otključaj postavke mreže"),
("Server", "Poslužitelj"),
("Direct IP Access", "Izravan IP pristup"),
("Proxy", "Proxy"),
("Apply", "Primijeni"),
("Disconnect all devices?", "Odspojiti sve uređaje?"),
("Clear", "Obriši"),
("Audio Input Device", "Uređaj za ulaz zvuka"),
("Use IP Whitelisting", "Koristi popis pouzdanih IP adresa"),
("Network", "Mreža"),
("Pin Toolbar", "Prikači alatnu traku"),
("Unpin Toolbar", "Otkvači alatnu traku"),
("Recording", "Snimanje"),
("Directory", "Mapa"),
("Automatically record incoming sessions", "Automatski snimi dolazne sesije"),
("Automatically record outgoing sessions", "Automatski snimi odlazne sesije"),
("Change", "Promijeni"),
("Start session recording", "Započni snimanje sesije"),
("Stop session recording", "Zaustavi snimanje sesije"),
("Enable recording session", "Omogući snimanje sesije"),
("Enable LAN discovery", "Omogući LAN otkrivanje"),
("Deny LAN discovery", "Onemogući LAN otkrivanje"),
("Write a message", "Napiši poruku"),
("Prompt", "Spremno"),
("Please wait for confirmation of UAC...", "Molimo pričekajte potvrdu UAC-a..."),
("elevated_foreground_window_tip", "Tekući prozor udaljene radne površine zahtijeva veće privilegije za rad, tako da trenutno nije moguće koristiti miša i tipkovnicu. Možete zatražiti od udaljenog korisnika da minimizira aktivni prozor, ili kliknuti gumb za povećanje privilegija u prozoru za upravljanje vezom. Kako biste izbjegli ovaj problem, preporučujemo da instalirate softver na udaljeni uređaj."),
("Disconnected", "Odspojeno"),
("Other", "Ostalo"),
("Confirm before closing multiple tabs", "Potvrda prije zatvaranja više kartica"),
("Keyboard Settings", "Postavke tipkovnice"),
("Full Access", "Potpuni pristup"),
("Screen Share", "Dijeljenje zaslona"),
("ubuntu-21-04-required", "Wayland zahtijeva Ubuntu verziju 21.04 ili višu"),
("wayland-requires-higher-linux-version", "Wayland zahtijeva višu verziju Linux distribucije. Molimo isprobjate X11 ili promijenite OS."),
("xdp-portal-unavailable", "Snimanje zaslona za Wayland nije uspjelo. XDG Desktop Portal se možda srušio ili je nedostupan. Pokušajte ga ponovno pokrenuti naredbom `systemctl --user restart xdg-desktop-portal`."),
("JumpLink", "Vidi"),
("Please Select the screen to be shared(Operate on the peer side).", "Molimo odaberite zaslon koji će biti podijeljen (Za rad na strani klijenta)"),
("Show RustDesk", "Prikaži RustDesk"),
("This PC", "Ovo računalo"),
("or", "ili"),
("Elevate", "Izdigni"),
("Zoom cursor", "Zumiraj kursor"),
("Accept sessions via password", "Prihvati sesije preko lozinke"),
("Accept sessions via click", "Prihvati sesije preko klika"),
("Accept sessions via both", "Prihvati sesije preko oboje"),
("Please wait for the remote side to accept your session request...", "Molimo pričekajte da udaljena strana prihvati vaš zahtjev za sesijom..."),
("One-time Password", "Jednokratna lozinka"),
("Use one-time password", "Koristi jednokratnu lozinku"),
("One-time password length", "Duljina jednokratne lozinke"),
("Request access to your device", "Zahtjev za pristup vašem uređaju"),
("Hide connection management window", "Sakrij prozor za uređivanje veze"),
("hide_cm_tip", "Skrivanje dozvoljeno samo prihvaćanjem sesije preko lozinke i korištenjem trajne lozinke"),
("wayland_experiment_tip", "Podrška za Wayland je eksperimentalna, ako trebate pristup bez nadzora, koristite X11."),
("Right click to select tabs", "Desni klik za odabir kartica"),
("Skipped", "Preskočeno"),
("Add to address book", "Dodaj u adresar"),
("Group", "Grupa"),
("Search", "Pretraga"),
("Closed manually by web console", "Zatvoreno ručno pomoću web konzole"),
("Local keyboard type", "Vrsta lokalne tipkovnice"),
("Select local keyboard type", "Odabir lokalne vrste tipkovnice"),
("software_render_tip", "Ako koristite Nvidia grafičku karticu na Linuxu i udaljeni prozor se zatvori odmah nakon povezivanja, prebacivanje na Nouveau upravljački program otvorenog kôda i odabir softverskog renderiranja može pomoći. Potrebno je ponovno pokretanje."),
("Always use software rendering", "Uvijek koristite softversko renderiranje"),
("config_input", "Za upravljanje udaljenom radnom površinom pomoću tipkovnice, morate dodijeliti RustDesku dopuštenje \"Nadzor unosa\"."),
("config_microphone", "Da biste razgovarali na daljinu, morate dopustiti RustDesku \"Snimanje zvuka\"."),
("request_elevation_tip", "Također možete tražiti podizanje ako je netko na drugoj strani."),
("Wait", "Pričekaj"),
("Elevation Error", "Pogreška povećanja"),
("Ask the remote user for authentication", "Pitajte udaljenog korisnika za autentifikaciju"),
("Choose this if the remote account is administrator", "Odaberite ovu opciju ako je udaljeni račun administrator"),
("Transmit the username and password of administrator", "Prijenos administratorskog korisničkog imena i lozinke"),
("still_click_uac_tip", "Još uvijek zahtijeva da udaljeni korisnik klikne OK u UAC prozoru pokrenutog RustDeska."),
("Request Elevation", "Zahtjev za podizanje"),
("wait_accept_uac_tip", "Pričekajte da udaljeni korisnik prihvati UAC dijaloški okvir."),
("Elevate successfully", "Uspješno podizanje"),
("uppercase", "velika slova"),
("lowercase", "mala slova"),
("digit", "brojka"),
("special character", "poseban znak"),
("length>=8", "duljina>=8"),
("Weak", "Slabo"),
("Medium", "Srednje"),
("Strong", "Jako"),
("Switch Sides", "Promjena strane"),
("Please confirm if you want to share your desktop?", "Potvrdite ako želite dijeliti svoju radnu površinu?"),
("Display", "Zaslon"),
("Default View Style", "Zadani način prikaza"),
("Default Scroll Style", "Zadani način pomaka"),
("Default Image Quality", "Zadana kvaliteta slike"),
("Default Codec", "Izlazni kodek"),
("Bitrate", "Tok podataka"),
("FPS", "FPS"),
("Auto", "Autom."),
("Other Default Options", "Ostale zadane opcije"),
("Voice call", "Glasovni poziv"),
("Text chat", "Tekstni chat"),
("Stop voice call", "Zaustavi glasovni poziv"),
("relay_hint_tip", "Izravna veza možda neće biti moguća, možete se pokušati povezati preko relejnog poslužitelja. Osim toga, ako želite koristiti poslužitelj za prosljeđivanje u prvom pokušaju, možete dodati sufiks ID-u \"/r\", ili u kartici nedavnih sesija odaberite opciju \"Uvijek se poveži preko pristupnika\", ako postoji."),
("Reconnect", "Ponovno se spojite"),
("Codec", "Kodek"),
("Resolution", "Razlika"),
("No transfers in progress", "Nema prijenosa u tijeku"),
("Set one-time password length", "Postavljanje duljine jednokratne lozinke"),
("RDP Settings", "Postavljanje RDP-a"),
("Sort by", "Poredaj po"),
("New Connection", "Nova veza"),
("Restore", "Vratiti"),
("Minimize", "Smanjiti"),
("Maximize", "Povećati"),
("Your Device", "Vaš uređaj"),
("empty_recent_tip", "Nema nedavne sesije!\nVrijeme je da zakažete novu."),
("empty_favorite_tip", "Još nemate nijednog omiljenog partnera?\nPronađite nekoga s kim se možete povezati i dodajte ga u svoje favorite!"),
("empty_lan_tip", "Ali ne, izgleda da još nismo otkrili niti jednu drugu stranu."),
("empty_address_book_tip", "Izgleda da trenutno nemate nijednog kolege navedenog u svom imeniku."),
("Empty Username", "Prazno korisničko ime"),
("Empty Password", "Prazna lozinka"),
("Me", "Ja"),
("identical_file_tip", "Ova je datoteka identična partnerskoj datoteci."),
("show_monitors_tip", "Prikažite monitore na alatnoj traci"),
("View Mode", "Način prikaza"),
("verify_rustdesk_password_tip", "Provjera lozinke za RustDesk"),
("No need to elevate", "Nije potrebno povećanje"),
("System Sound", "Zvuk sustava"),
("Default", "Zadano"),
("New RDP", "Novi RDP"),
("Fingerprint", "Otisak"),
("Copy Fingerprint", "Kopirat otisak"),
("no fingerprints", "nema otiska"),
("Update", "Ažuriraj"),
("resolution_original_tip", "Izvorna rezolucija"),
("resolution_fit_local_tip", "Podesite lokalnu rezoluciju"),
("resolution_custom_tip", "Prilagođena rezolucija"),
("Collapse toolbar", "Sažmi alatnu traku"),
("Accept and Elevate", "Prihvati povećanje"),
("accept_and_elevate_btn_tooltip", "Prihvatite vezu i povećajte UAC dopuštenja."),
("clipboard_wait_response_timeout_tip", "Isteklo je vrijeme čekanja na kopiju odgovora."),
("Incoming connection", "Dolazna veza"),
("Outgoing connection", "Odlazna veza"),
("Exit", "Izlaz"),
("Open", "Otvori"),
("logout_tip", "Jeste li sigurni da se želite odjaviti?"),
("Service", "Servis"),
("Start", "Pokreni"),
("Stop", "Zaustavi"),
("exceed_max_devices", "Dosegli ste najveći broj upravljanih uređaja."),
("Sync with recent sessions", "Sinkronizacija s nedavnim sesijama"),
("Sort tags", "Razvrstaj oznake"),
("Open connection in new tab", "Otvorite vezu u novoj kartici"),
("Move tab to new window", "Premjesti karticu u novi prozor"),
("Can not be empty", "Ne može biti prazno"),
("Already exists", "Već postoji"),
("Change Password", "Promjena lozinke"),
("Refresh Password", "Poništavanje lozinke"),
("ID", "ID"),
("Grid View", "Mreža"),
("List View", "Imenik"),
("Select", "Odaberi"),
("Toggle Tags", "Promijenite oznake"),
("pull_ab_failed_tip", "Nije uspjelo vraćanje imenika"),
("push_ab_failed_tip", "Sinkronizacija imenika s poslužiteljem nije uspjela"),
("synced_peer_readded_tip", "Uređaji koji su bili prisutni u posljednjim sesijama sinkronizirat će se natrag u imenik."),
("Change Color", "Promjena boje"),
("Primary Color", "Osnovna boja"),
("HSV Color", "HSV boja"),
("Installation Successful!", "Instalacija uspjela!"),
("Installation failed!", "Instalacija nije uspjela!"),
("Reverse mouse wheel", "Obrnuti kotačić miša"),
("{} sessions", "{} sesija"),
("scam_title", "Možda vas je netko PREVARIO!"),
("scam_text1", "Ako razgovarate telefonom s nekim koga NE POZNAJETE i NE VJERUJETE tko vas je zamolio da koristite i pokrenete RustDesk, nemojte nastavljati razgovor i odmah spustite slušalicu."),
("scam_text2", "Ovo je vjerojatno prevarant koji pokušava ukrasti vaš novac ili druge privatne podatke."),
("Don't show again", "Ne prikazuj opet"),
("I Agree", "Slažem se"),
("Decline", "Ne slažem se"),
("Timeout in minutes", "Istek u minutama"),
("auto_disconnect_option_tip", "Automatsko prekidanje dolaznih veza kada je korisnik neaktivan"),
("Connection failed due to inactivity", "Povezivanje nije uspjelo zbog neaktivnosti"),
("Check for software update on startup", "Provjera ažuriranja softvera pri pokretanju"),
("upgrade_rustdesk_server_pro_to_{}_tip", "Ažurirajte RustDesk Server Pro na verziju {} ili noviju!"),
("pull_group_failed_tip", "Vraćanje grupe nije uspjelo"),
("Filter by intersection", "Filtriraj po prosjeku"),
("Remove wallpaper during incoming sessions", "Uklonite pozadinu tijekom dolaznih sesija"),
("Test", "Test"),
("display_is_plugged_out_msg", "Zaslon je isključen, prijeđite na prvi zaslon."),
("No displays", "Nema zaslona"),
("Open in new window", "Otvori u novom prozoru"),
("Show displays as individual windows", "Prikaži zaslone kao pojedinačne prozore"),
("Use all my displays for the remote session", "Koristi sve moje zaslone za udaljenu sesiju"),
("selinux_tip", "Na vašem uređaju je omogućen SELinux, što može spriječiti RustDesk da pravilno radi kao upravljana strana."),
("Change view", "Promjena prikaza"),
("Big tiles", "Velike pločice"),
("Small tiles", "Male pločice"),
("List", "Imenik"),
("Virtual display", "Virtualni zaslon"),
("Plug out all", "Odspojite sve"),
("True color (4:4:4)", "Stvarne boje (4:4:4)"),
("Enable blocking user input", "Omogući blokiranje korisničkog unosa"),
("id_input_tip", "Možete unijeti ID, izravnu IP adresu ili domenu s portom (<domena>:<port>).\nAko želite pristupiti uređaju na drugom poslužitelju, povežite adresu poslužitelja (<id>@<adresa_poslužitelja>?kljuć=<vrijednost_ključa>), naprimjer,\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nAko želite pristupiti uređaju na javnom poslužitelju, unesite \"<id>@public\", ključ nije potreban za javni poslužitelj."),
("privacy_mode_impl_mag_tip", "Način 1"),
("privacy_mode_impl_virtual_display_tip", "Način 2"),
("Enter privacy mode", "Uđite u način privatnosti"),
("Exit privacy mode", "Izađi iz načina privatnosti"),
("idd_not_support_under_win10_2004_tip", "Neizravni upravljački program za zaslon nije podržan. Potreban je Windows 10 verzija 2004 ili novija."),
("input_source_1_tip", "Ulazni izvor 1"),
("input_source_2_tip", "Ulazni izvor 2"),
("Swap control-command key", "Zamjena tipki control-command"),
("swap-left-right-mouse", "Zamjena lijeve i desne tipke miša"),
("2FA code", "2FA kôd"),
("More", "Više"),
("enable-2fa-title", "Omogući dvofaktorsku autentifikaciju"),
("enable-2fa-desc", "Postavite svoj autentifikator. Na telefonu ili računalu možete koristiti aplikaciju za autentifikaciju kao što su Authy, Microsoft ili Google Authenticator.\n\nSkenirajte QR kôd pomoću aplikacije i unesite kôd koji aplikacija prikazuje za aktiviranje dvofaktorske autentifikacije."),
("wrong-2fa-code", "Kôd se ne može provjeriti. Provjerite jesu li kôd i postavke lokalnog vremena točni"),
("enter-2fa-title", "Dvofaktorska autentifikacija"),
("Email verification code must be 6 characters.", "Kôd za provjeru e-pošte mora imati 6 znakova."),
("2FA code must be 6 digits.", "2FA kôd mora imati 6 znamenki."),
("Multiple Windows sessions found", "Pronađeno je više Windows sesija"),
("Please select the session you want to connect to", "Odaberite sesiju kojoj se želite pridružiti"),
("powered_by_me", "Pokreće RustDesk"),
("outgoing_only_desk_tip", "Ovo je prilagođeno izdanje.\nMožete se povezati s drugim uređajima, ali se drugi uređaji ne mogu povezati s vašim uređajem."),
("preset_password_warning", "Ovo modificirano izdanje dolazi s unaprijed postavljenom lozinkom. Svatko tko zna ovu lozinku može dobiti potpunu kontrolu nad vašim uređajem. Ako to niste očekivali, odmah deinstalirajte softver."),
("Security Alert", "Sigurnosno upozorenje"),
("My address book", "Moj adresar"),
("Personal", "Osobni"),
("Owner", "Vlasnik"),
("Set shared password", "Postavite zajedničku lozinku"),
("Exist in", "Postoji u"),
("Read-only", "Samo za čitanje"),
("Read/Write", "Način čitanja/pisanja"),
("Full Control", "Potpuna kontrola"),
("share_warning_tip", "Gornja polja su podijeljena i vidljiva drugima."),
("Everyone", "Svatko"),
("ab_web_console_tip", "Više na web konzoli"),
("allow-only-conn-window-open-tip", "Dopusti vezu samo ako je prozor RustDeska otvoren"),
("no_need_privacy_mode_no_physical_displays_tip", "Nema fizičkih zaslona, nema potrebe za korištenjem načina privatnosti."),
("Follow remote cursor", "Prati udaljeni kursor"),
("Follow remote window focus", "Prati fokus udaljenog prozora"),
("default_proxy_tip", "Zadani protokol i priključak su Socks5 i 1080"),
("no_audio_input_device_tip", "Nije pronađen ulazni audio uređaj."),
("Incoming", "Dolazno"),
("Outgoing", "Odlazno"),
("Clear Wayland screen selection", "Očisti odabir zaslona za Wayland"),
("clear_Wayland_screen_selection_tip", "Nakon brisanja odabira zaslona možete ponovno odabrati zaslon za dijeljenje."),
("confirm_clear_Wayland_screen_selection_tip", "Jeste li sigurni da želite obrisati odabir zaslona za Wayland?"),
("android_new_voice_call_tip", "Primljen je novi zahtjev za glasovni poziv. Ako ga prihvatite, zvuk će se prebaciti na glasovnu komunikaciju."),
("texture_render_tip", "Koristite renderiranje tekstura kako bi slike bile glađe. Možete pokušati onemogućiti ovu opciju ako naiđete na probleme s renderiranjem."),
("Use texture rendering", "Koristi renderiranje tekstura"),
("Floating window", "Plutajući prozor"),
("floating_window_tip", "Pomaže u održavanju pozadinskog servisa RustDeska"),
("Keep screen on", "Zadrži zaslon uključenim"),
("Never", "Nikad"),
("During controlled", "Tijekom upravljanja"),
("During service is on", "Dok je servis uključen"),
("Capture screen using DirectX", "Snimaj zaslon pomoću DirectX-a"),
("Back", "Natrag"),
("Apps", "Aplikacije"),
("Volume up", "Pojačaj glasnoću"),
("Volume down", "Smanji glasnoću"),
("Power", "Napajanje"),
("Telegram bot", "Telegram bot"),
("enable-bot-tip", "Ako omogućite ovu značajku, možete primati 2FA kôd od svog bota. Može poslužiti i kao obavijest o vezi."),
("enable-bot-desc", "1. Otvorite razgovor s @BotFather.\n2. Pošaljite naredbu \"/newbot\". Nakon dovršetka ovog koraka primit ćete token.\n3. Započnite razgovor s novostvorenim botom. Pošaljite poruku koja počinje kosom crtom (\"/\"), poput \"/hello\", kako biste ga aktivirali.\n"),
("cancel-2fa-confirm-tip", "Jeste li sigurni da želite otkazati 2FA?"),
("cancel-bot-confirm-tip", "Jeste li sigurni da želite otkazati Telegram bota?"),
("About RustDesk", "O RustDesku"),
("Send clipboard keystrokes", "Pošalji pritiske tipki iz međuspremnika"),
("network_error_tip", "Provjerite svoju mrežnu vezu, a zatim kliknite Pokušaj ponovno."),
("Unlock with PIN", "Otključaj PIN-om"),
("Requires at least {} characters", "Potrebno je najmanje {} znakova"),
("Wrong PIN", "Pogrešan PIN"),
("Set PIN", "Postavi PIN"),
("Enable trusted devices", "Omogući pouzdane uređaje"),
("Manage trusted devices", "Upravljaj pouzdanim uređajima"),
("Platform", "Platforma"),
("Days remaining", "Preostalo dana"),
("enable-trusted-devices-tip", "Preskoči 2FA provjeru na pouzdanim uređajima"),
("Parent directory", "Nadređeni direktorij"),
("Resume", "Nastavi"),
("Invalid file name", "Nevažeći naziv datoteke"),
("one-way-file-transfer-tip", "Jednosmjerni prijenos datoteka omogućen je na upravljanoj strani."),
("Authentication Required", "Potrebna autentifikacija"),
("Authenticate", "Autentificiraj"),
("web_id_input_tip", "Možete unijeti ID na istom poslužitelju, izravan pristup preko IP adrese nije podržan u web klijentu.\nAko želite pristupiti uređaju na drugom poslužitelju, dodajte adresu poslužitelja (<id>@<server_address>?key=<key_value>), na primjer,\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nAko želite pristupiti uređaju na javnom poslužitelju, unesite \"<id>@public\", ključ nije potreban za javni poslužitelj."),
("Download", "Preuzmi"),
("Upload folder", "Prenesi mapu"),
("Upload files", "Prenesi datoteke"),
("Clipboard is synchronized", "Međuspremnik je sinkroniziran"),
("Update client clipboard", "Ažuriraj međuspremnik klijenta"),
("Untagged", "Bez oznake"),
("new-version-of-{}-tip", "Dostupna je nova verzija {}"),
("Accessible devices", "Dostupni uređaji"),
("upgrade_remote_rustdesk_client_to_{}_tip", "Molimo ažurirajte RustDesk klijent na verziju {} ili noviju na udaljenoj strani!"),
("d3d_render_tip", "Kada je omogućeno D3D renderiranje, na nekim računalima zaslon daljinskog upravljanja može biti crn."),
("Use D3D rendering", "Koristi D3D renderiranje"),
("Printer", "Pisač"),
("printer-os-requirement-tip", "Funkcija odlaznog ispisa zahtijeva Windows 10 ili noviju verziju."),
("printer-requires-installed-{}-client-tip", "Za korištenje udaljenog ispisa, na ovom uređaju mora biti instaliran {}."),
("printer-{}-not-installed-tip", "Pisač {} nije instaliran."),
("printer-{}-ready-tip", "Pisač {} je instaliran i spreman za korištenje."),
("Install {} Printer", "Instaliraj pisač {}"),
("Outgoing Print Jobs", "Odlazni zadaci ispisa"),
("Incoming Print Jobs", "Dolazni zadaci ispisa"),
("Incoming Print Job", "Dolazni zadatak ispisa"),
("use-the-default-printer-tip", "Koristi zadani pisač"),
("use-the-selected-printer-tip", "Koristi odabrani pisač"),
("auto-print-tip", "Automatski ispisuj pomoću odabranog pisača."),
("print-incoming-job-confirm-tip", "Primili ste zadatak ispisa s udaljenog uređaja. Želite li ga izvršiti na svojoj strani?"),
("remote-printing-disallowed-tile-tip", "Udaljeni ispis nije dopušten"),
("remote-printing-disallowed-text-tip", "Postavke dozvola upravljane strane onemogućuju udaljeni ispis."),
("save-settings-tip", "Spremi postavke"),
("dont-show-again-tip", "Ne prikazuj ovo ponovno"),
("Take screenshot", "Snimi zaslon"),
("Taking screenshot", "Snimanje zaslona"),
("screenshot-merged-screen-not-supported-tip", "Spajanje snimaka zaslona s više zaslona trenutačno nije podržano. Prebacite se na jedan zaslon i pokušajte ponovno."),
("screenshot-action-tip", "Odaberite kako nastaviti sa snimkom zaslona."),
("Save as", "Spremi kao"),
("Export", "Izvoz"),
("Export Logs", "Izvoz zapisnika"),
("Import Folder", "Uvoz mape"),
("Copy to clipboard", "Kopiraj u međuspremnik"),
("Enable remote printer", "Omogući udaljeni pisač"),
("Downloading {}", "Preuzimanje {}"),
("{} Update", "Ažuriranje {}"),
("{}-to-update-tip", "{} će se sada zatvoriti i instalirati novu verziju."),
("download-new-version-failed-tip", "Preuzimanje nije uspjelo. Možete pokušati ponovno ili kliknuti gumb \"Preuzmi\" za preuzimanje sa stranice izdanja i ručnu nadogradnju."),
("Auto update", "Automatsko ažuriranje"),
("update-failed-check-msi-tip", "Provjera načina instalacije nije uspjela. Kliknite gumb \"Preuzmi\" za preuzimanje sa stranice izdanja i ručnu nadogradnju."),
("websocket_tip", "Kada koristite WebSocket, podržane su samo relejne veze."),
("Use WebSocket", "Koristi WebSocket"),
("Trackpad speed", "Brzina dodirne ploče"),
("Default trackpad speed", "Zadana brzina dodirne ploče"),
("Numeric one-time password", "Numerička jednokratna lozinka"),
("Enable IPv6 P2P connection", "Omogući IPv6 P2P vezu"),
("Enable UDP hole punching", "Omogući UDP hole punching"),
("View camera", "Pregled kamere"),
("Enable camera", "Omogući kameru"),
("No cameras", "Nema kamera"),
("view_camera_unsupported_tip", "Udaljeni uređaj ne podržava pregled kamere."),
("Terminal", "Terminal"),
("Enable terminal", "Omogući terminal"),
("New tab", "Nova kartica"),
("Keep terminal sessions on disconnect", "Zadrži sesije terminala pri prekidu veze"),
("Terminal (Run as administrator)", "Terminal (Pokreni kao administrator)"),
("terminal-admin-login-tip", "Unesite administratorsko korisničko ime i lozinku upravljane strane."),
("Failed to get user token.", "Nije uspjelo dohvaćanje korisničkog tokena."),
("Incorrect username or password.", "Netočno korisničko ime ili lozinka."),
("The user is not an administrator.", "Korisnik nije administrator."),
("Failed to check if the user is an administrator.", "Nije uspjela provjera je li korisnik administrator."),
("Supported only in the installed version.", "Podržano samo u instaliranoj verziji."),
("elevation_username_tip", "Unesite korisničko ime ili domena\\korisničko ime"),
("Preparing for installation ...", "Priprema za instalaciju ..."),
("Show my cursor", "Prikaži moj kursor"),
("Scale custom", "Prilagođeno skaliranje"),
("Custom scale slider", "Klizač prilagođenog skaliranja"),
("Decrease", "Smanji"),
("Increase", "Povećaj"),
("Show virtual mouse", "Prikaži virtualnog miša"),
("Virtual mouse size", "Veličina virtualnog miša"),
("Small", "Malo"),
("Large", "Veliko"),
("Show virtual joystick", "Prikaži virtualni joystick"),
("Edit note", "Uredi bilješku"),
("Alias", "Alias"),
("ScrollEdge", "ScrollEdge"),
("Allow insecure TLS fallback", "Dopusti nesigurni TLS pričuvni način"),
("allow-insecure-tls-fallback-tip", "Prema zadanim postavkama, RustDesk provjerava certifikat poslužitelja za protokole koji koriste TLS.\nKada je ova opcija omogućena, RustDesk će u slučaju neuspjele provjere preskočiti korak provjere i nastaviti."),
("Disable UDP", "Onemogući UDP"),
("disable-udp-tip", "Određuje hoće li se koristiti samo TCP.\nKada je ova opcija omogućena, RustDesk više neće koristiti UDP 21116, već će umjesto toga koristiti TCP 21116."),
("server-oss-not-support-tip", "NAPOMENA: RustDesk poslužitelj OSS ne uključuje ovu značajku."),
("input note here", "ovdje unesite bilješku"),
("note-at-conn-end-tip", "Zatraži bilješku na kraju veze"),
("Show terminal extra keys", "Prikaži dodatne tipke terminala"),
("Relative mouse mode", "Relativni način miša"),
("rel-mouse-not-supported-peer-tip", "Povezani uređaj ne podržava relativni način miša."),
("rel-mouse-not-ready-tip", "Relativni način miša još nije spreman. Pokušajte ponovno."),
("rel-mouse-lock-failed-tip", "Zaključavanje kursora nije uspjelo. Relativni način miša je onemogućen."),
("rel-mouse-exit-{}-tip", "Pritisnite {} za izlaz."),
("rel-mouse-permission-lost-tip", "Dozvola za tipkovnicu je opozvana. Relativni način miša je onemogućen."),
("Changelog", "Popis promjena"),
("keep-awake-during-outgoing-sessions-label", "Zadrži zaslon aktivnim tijekom odlaznih sesija"),
("keep-awake-during-incoming-sessions-label", "Zadrži zaslon aktivnim tijekom dolaznih sesija"),
("Continue with {}", "Nastavi sa {}"),
("Display Name", "Prikazani naziv"),
("password-hidden-tip", "Trajna lozinka je postavljena (skrivena)."),
("preset-password-in-use-tip", "Unaprijed postavljena lozinka trenutačno je u upotrebi."),
("Enable privacy mode", "Omogući način privatnosti"),
("allow-remote-toolbar-docking-any-edge", "Dopusti usidrenje udaljene alatne trake na bilo koji rub prozora"),
("API Token", "API token"),
("Deploy", "Postavi"),
("Custom ID (optional)", "Prilagođeni ID (neobavezno)"),
("server_requires_deployment_tip", "Poslužitelj zahtijeva da se ovaj uređaj eksplicitno postavi. Postaviti sada?"),
("The server does not require explicit deployment.", "Poslužitelj ne zahtijeva eksplicitno postavljanje."),
("Unknown response.", "Nepoznat odgovor."),
("wayland-keyboard-input-disabled-tip", "Dopustiti unos tipkovnicom?"),
("wayland-keyboard-input-consent-tip", "Ono što tipkate na ovom udaljenom računalu (uključujući lozinke) mogle bi pročitati druge aplikacije na njemu."),
("wayland-keyboard-input-applies-to-tip", "Ovaj izbor odnosi se na:"),
("wayland-soft-keyboard-input-label", "Unos softverskom tipkovnicom"),
("wayland-keyboard-input-reset-choice-tip", "Poništi izbor unosa tipkovnicom"),
("remember-wayland-keyboard-choice-tip", "Ne pitaj ponovno za ovo udaljeno računalo"),
("Why this happens", "Zašto se ovo događa"),
("Switch display", "Promijeni zaslon"),
("Show monitor switch button on the main toolbar", "Prikaži gumb za prebacivanje monitora na glavnoj alatnoj traci"),
("Show on the minimized toolbar", "Prikaži na minimiziranoj alatnoj traci"),
("All monitors", "Svi monitori"),
("#{} monitor", "Monitor {}"),
("conn-e2ee-unavailable-tip", "End-to-end enkripcija nije mogla biti potvrđena.\nUdaljeni uređaj se možda još postavlja. Pokušajte ponovno kasnije.\nAko se to nastavi događati, poslužitelj možda nije pouzdan.\nIpak nastaviti?"),
("ID whitelisting", "ID pouzdana lista"),
("Use ID whitelisting", "Koristi popis pouzdanih ID-ova"),
("id_whitelist_tip", "Mogu mi pristupiti samo dozvoljeni ID-ovi"),
("id_whitelist_wildcard_tip", "Podržani su zamjenski znakovi: '*' odgovara bilo kojem broju znakova, '?' točno jednom znaku"),
("Invalid ID", "Nevažeći ID"),
("Your ID is blocked by the peer", "Vaš ID je blokiralo udaljeno računalo"),
("Your ip is blocked by the peer", "Vašu IP adresu je blokiralo udaljeno računalo"),
("id_whitelist_caveat_tip", "ID prijavljuje klijent koji se povezuje. Ova lista smanjuje izloženost i ne zamjenjuje lozinku ni 2FA"),
("whitelist_cidr_tip", "Podržan je CIDR zapis, primjerice 192.168.1.0/24"),
("Continue", "Nastavi"),
("Browser didn't open? Use the url below to sign in.", "Preglednik se nije otvorio? Za prijavu upotrijebite URL u nastavku."),
("Lock canvas", "Zaključaj pozadinu"),
("Sync clipboard between sessions", "Sinkroniziraj međuspremnik između sesija"),
("sync-clipboard-between-sessions-tip", "Tekst ili slike kopirani u jednoj udaljenoj sesiji šalju se i u međuspremnik vaših ostalih povezanih sesija."),
("terminal-clipboard-write-tip", ""),
("Allow terminal apps to copy to clipboard", ""),
("Enable", "Omogući"),
("Reuse one connection for port forwarding", "Ponovno koristi jednu vezu za prosljeđivanje portova"),
("port-forward-mux-tip", "Sve veze jednog prosljeđivanja portova idu kroz jednu vezu prema drugoj strani, umjesto ponovnog povezivanja i prijave za svaku od njih."),
("Enable WebRTC P2P connection", "Omogući WebRTC P2P vezu"),
("Enable TCP hole punching", "Omogući TCP hole punching"),
].iter().cloned().collect();
}