mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-10-19 16:17:03 +00:00
* 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>
775 lines
50 KiB
Rust
775 lines
50 KiB
Rust
lazy_static::lazy_static! {
|
|
pub static ref T: std::collections::HashMap<&'static str, &'static str> =
|
|
[
|
|
("Status", "Status"),
|
|
("Your Desktop", "Desktop Anda"),
|
|
("desk_tip", "Akses desktop kamu dengan ID & Kata sandi ini"),
|
|
("Password", "Kata sandi"),
|
|
("Ready", "Sudah siap"),
|
|
("Established", "Didirikan"),
|
|
("connecting_status", "Menghubungkan ke RustDesk..."),
|
|
("Enable service", "Aktifkan Layanan"),
|
|
("Start service", "Mulai Layanan"),
|
|
("Service is running", "Layanan berjalan"),
|
|
("Service is not running", "Layanan tidak berjalan"),
|
|
("not_ready_status", "Belum siap digunakan. Silakan periksa koneksi"),
|
|
("Control Remote Desktop", "Lakukan Kontrol PC dari jarak jauh"),
|
|
("Transfer file", "Transfer File"),
|
|
("Connect", "Sambungkan"),
|
|
("Recent sessions", "Sesi Terkini"),
|
|
("Address book", "Buku Alamat"),
|
|
("Confirmation", "Konfirmasi"),
|
|
("TCP tunneling", "Tunneling TCP"),
|
|
("Remove", "Hapus"),
|
|
("Refresh random password", "Perbarui kata sandi acak"),
|
|
("Set your own password", "Tetapkan kata sandi"),
|
|
("Enable keyboard/mouse", "Aktifkan Keyboard/Mouse"),
|
|
("Enable clipboard", "Aktifkan Papan Klip"),
|
|
("Enable file transfer", "Aktifkan Transfer file"),
|
|
("Enable TCP tunneling", "Aktifkan TCP tunneling"),
|
|
("IP Whitelisting", "Daftar IP yang diizinkan"),
|
|
("ID/Relay Server", "ID/Relay Server"),
|
|
("Import server config", "Impor Konfigurasi Server"),
|
|
("Export Server Config", "Ekspor Konfigurasi Server"),
|
|
("Import server configuration successfully", "Impor konfigurasi server berhasil"),
|
|
("Export server configuration successfully", "Ekspor konfigurasi server berhasil"),
|
|
("Invalid server configuration", "Konfigurasi server tidak valid"),
|
|
("Clipboard is empty", "Papan klip kosong"),
|
|
("Stop service", "Hentikan Layanan"),
|
|
("Change ID", "Ubah ID"),
|
|
("Your new ID", "ID baru"),
|
|
("length %min% to %max%", "panjang %min% s/d %max%"),
|
|
("starts with a letter", "Dimulai dengan huruf"),
|
|
("allowed characters", "Karakter yang dapat digunakan"),
|
|
("id_change_tip", "Hanya karakter a-z, A-Z, 0-9, - (dash) dan _ (underscore) yang diperbolehkan. Huruf pertama harus a-z, A-Z. Panjang antara 6 dan 16."),
|
|
("Website", "Situs Web"),
|
|
("About", "Tentang"),
|
|
("Slogan_tip", "Dibuat dengan penuh kasih sayang dalam dunia yang penuh kekacauan ini"),
|
|
("Privacy Statement", "Pernyataan Privasi"),
|
|
("Mute", "Bisukan"),
|
|
("Build Date", "Tanggal Build"),
|
|
("Version", "Versi"),
|
|
("Home", "Beranda"),
|
|
("Audio Input", "Input Audio"),
|
|
("Enhancements", "Peningkatan"),
|
|
("Hardware Codec", "Kodek Perangkat Keras"),
|
|
("Adaptive bitrate", "Kecepatan Bitrate Adaptif"),
|
|
("ID Server", "Server ID"),
|
|
("Relay Server", "Server Relay"),
|
|
("API Server", "Server API"),
|
|
("invalid_http", "harus dimulai dengan http:// atau https://"),
|
|
("Invalid IP", "IP tidak valid"),
|
|
("Invalid format", "Format tidak valid"),
|
|
("server_not_support", "Belum didukung oleh server"),
|
|
("Not available", "Tidak tersedia"),
|
|
("Too frequent", "Terlalu sering"),
|
|
("Cancel", "Batal"),
|
|
("Skip", "Lanjutkan"),
|
|
("Close", "Tutup"),
|
|
("Retry", "Coba lagi"),
|
|
("OK", "Oke"),
|
|
("Password Required", "Kata sandi tidak boleh kosong"),
|
|
("Please enter your password", "Silahkan masukkan kata sandi"),
|
|
("Remember password", "Ingat kata sandi"),
|
|
("Wrong Password", "Kata sandi Salah"),
|
|
("Do you want to enter again?", "Apakah kamu ingin mencoba lagi?"),
|
|
("Connection Error", "Kesalahan koneksi"),
|
|
("Error", "Kesalahan"),
|
|
("Reset by the peer", "Direset oleh rekan"),
|
|
("Connecting...", "Menghubungkan..."),
|
|
("Connection in progress. Please wait.", "Koneksi sedang berlangsung. Mohon tunggu."),
|
|
("Please try 1 minute later", "Silahkan coba 1 menit lagi"),
|
|
("Login Error", "Kesalahan Login"),
|
|
("Successful", "Berhasil"),
|
|
("Connected, waiting for image...", "Terhubung, menunggu gambar..."),
|
|
("Name", "Nama"),
|
|
("Type", "Tipe"),
|
|
("Modified", "Diperbarui"),
|
|
("Size", "Ukuran"),
|
|
("Show Hidden Files", "Tampilkan File Tersembunyi"),
|
|
("Receive", "Menerima"),
|
|
("Send", "Kirim"),
|
|
("Refresh File", "Segarkan File"),
|
|
("Local", "Lokal"),
|
|
("Remote", "Remote"),
|
|
("Remote Computer", "Remote Komputer"),
|
|
("Local Computer", "Lokal Komputer"),
|
|
("Confirm Delete", "Konfirmasi Hapus"),
|
|
("Delete", "Hapus"),
|
|
("Properties", "Properti"),
|
|
("Multi Select", "Pilih Beberapa"),
|
|
("Select All", "Pilih Semua"),
|
|
("Unselect All", "Batalkan Pilihan Semua"),
|
|
("Empty Directory", "Folder Kosong"),
|
|
("Not an empty directory", "Folder tidak kosong"),
|
|
("Are you sure you want to delete this file?", "Apakah kamu yakin untuk menghapus file ini?"),
|
|
("Are you sure you want to delete this empty directory?", "Apakah yakin yakin untuk menghapus folder ini?"),
|
|
("Are you sure you want to delete the file of this directory?", "Apakah yakin yakin untuk menghapus file dan folder ini?"),
|
|
("Do this for all conflicts", "Lakukan untuk semua konflik"),
|
|
("This is irreversible!", "Ini tidak dapat diubah!"),
|
|
("Deleting", "Menghapus"),
|
|
("files", "file"),
|
|
("Waiting", "Menunggu"),
|
|
("Finished", "Selesai"),
|
|
("Speed", "Kecepatan"),
|
|
("Custom Image Quality", "Sesuaikan Kualitas Gambar"),
|
|
("Privacy mode", "Mode Privasi"),
|
|
("Block user input", "Blokir input pengguna"),
|
|
("Unblock user input", "Jangan blokir input pengguna"),
|
|
("Adjust Window", "Sesuaikan Jendela"),
|
|
("Original", "Asli"),
|
|
("Shrink", "Susutkan"),
|
|
("Stretch", "Regangkan"),
|
|
("Scrollbar", "Scrollbar"),
|
|
("ScrollAuto", "Scroll Otomatis"),
|
|
("Good image quality", "Kualitas Gambar Baik"),
|
|
("Balanced", "Seimbang"),
|
|
("Optimize reaction time", "Optimalkan waktu reaksi"),
|
|
("Custom", "Kustom"),
|
|
("Show remote cursor", "Tampilkan kursor remote"),
|
|
("Show quality monitor", "Tampilkan kualitas monitor"),
|
|
("Disable clipboard", "Matikan papan klip"),
|
|
("Lock after session end", "Kunci setelah sesi berakhir"),
|
|
("Insert Ctrl + Alt + Del", "Menyisipkan Ctrl + Alt + Del"),
|
|
("Insert Lock", "Masukkan Kunci"),
|
|
("Refresh", "Segarkan"),
|
|
("ID does not exist", "ID tidak ada"),
|
|
("Failed to connect to rendezvous server", "Gagal menghubungkan ke rendezvous server"),
|
|
("Please try later", "Silahkan coba lagi nanti"),
|
|
("Remote desktop is offline", "Remote desktop offline"),
|
|
("Key mismatch", "Ketidakcocokan kunci"),
|
|
("Timeout", "Waktu habis"),
|
|
("Failed to connect to relay server", "Gagal terkoneksi ke relay server"),
|
|
("Failed to connect via rendezvous server", "Gagal terkoneksi via rendezvous server"),
|
|
("Failed to connect via relay server", "Gagal terkoneksi via relay server"),
|
|
("Failed to make direct connection to remote desktop", "Gagal membuat koneksi langsung ke desktop jarak jauh"),
|
|
("Set Password", "Tetapkan kata sandi"),
|
|
("OS Password", "Kata Sandi OS"),
|
|
("install_tip", "Karena UAC, RustDesk tidak dapat bekerja dengan baik sebagai sisi remote dalam beberapa kasus. Untuk menghindari UAC, silakan klik tombol di bawah ini untuk menginstal RustDesk ke sistem."),
|
|
("Click to upgrade", "Klik untuk upgrade"),
|
|
("Configure", "Konfigurasi"),
|
|
("config_acc", "Agar bisa mengontrol Desktopmu dari jarak jauh, Kamu harus memberikan izin \"Aksesibilitas\" untuk RustDesk."),
|
|
("config_screen", "Agar bisa mengakses Desktopmu dari jarak jauh, kamu harus memberikan izin \"Perekaman Layar\" untuk RustDesk."),
|
|
("Installing ...", "Menginstall"),
|
|
("Install", "Instal"),
|
|
("Installation", "Instalasi"),
|
|
("Installation Path", "Direktori Instalasi"),
|
|
("Create start menu shortcuts", "Buat pintasan start menu"),
|
|
("Create desktop icon", "Buat icon desktop"),
|
|
("agreement_tip", "Dengan memulai proses instalasi, Kamu menerima perjanjian lisensi."),
|
|
("Accept and Install", "Terima dan Install"),
|
|
("End-user license agreement", "Perjanjian lisensi pengguna"),
|
|
("Generating ...", "Memproses..."),
|
|
("Your installation is lower version.", "Kamu menggunakan versi instalasi yang lebih rendah."),
|
|
("not_close_tcp_tip", "Pastikan jendela ini tetap terbuka saat menggunakan tunnel."),
|
|
("Listening ...", "Menghubungkan..."),
|
|
("Remote Host", "Host Remote"),
|
|
("Remote Port", "Port Remote"),
|
|
("Action", "Tindakan"),
|
|
("Add", "Tambah"),
|
|
("Local Port", "Port Lokal"),
|
|
("Local Address", "Alamat lokal"),
|
|
("Change Local Port", "Ubah Port Lokal"),
|
|
("setup_server_tip", "Untuk koneksi yang lebih baik, silakan konfigurasi di server pribadi"),
|
|
("Too short, at least 6 characters.", "Terlalu pendek, setidaknya 6 karekter."),
|
|
("The confirmation is not identical.", "Konfirmasi tidak identik."),
|
|
("Permissions", "Perizinan"),
|
|
("Accept", "Terima"),
|
|
("Dismiss", "Hentikan"),
|
|
("Disconnect", "Terputus"),
|
|
("Enable file copy and paste", "Izinkan copy dan paste"),
|
|
("Connected", "Terhubung"),
|
|
("Direct and encrypted connection", "Koneksi langsung dan terenkripsi"),
|
|
("Relayed and encrypted connection", "Koneksi relay dan terenkripsi"),
|
|
("Direct and unencrypted connection", "Koneksi langsung dan tanpa enkripsi"),
|
|
("Relayed and unencrypted connection", "Koneksi relay dan tanpa enkripsi"),
|
|
("Enter Remote ID", "Masukkan ID Remote"),
|
|
("Enter your password", "Masukkan kata sandi"),
|
|
("Logging in...", "Masuk..."),
|
|
("Enable RDP session sharing", "Aktifkan berbagi sesi RDP"),
|
|
("Auto Login", "Login Otomatis (Hanya berlaku jika sudah mengatur \"Kunci setelah sesi berakhir\")"),
|
|
("Enable direct IP access", "Aktifkan Akses IP Langsung"),
|
|
("Rename", "Ubah nama"),
|
|
("Space", "Spasi"),
|
|
("Create desktop shortcut", "Buat Pintasan Desktop"),
|
|
("Change Path", "Ubah Direktori"),
|
|
("Create Folder", "Buat Folder"),
|
|
("Please enter the folder name", "Silahkan masukkan nama folder"),
|
|
("Fix it", "Perbaiki"),
|
|
("Warning", "Peringatan"),
|
|
("Login screen using Wayland is not supported", "Login screen dengan Wayland tidak didukung"),
|
|
("Reboot required", "Diperlukan boot ulang"),
|
|
("Unsupported display server", "Server tampilan tidak didukung "),
|
|
("x11 expected", "Diperlukan x11"),
|
|
("Port", "Port"),
|
|
("Settings", "Pengaturan"),
|
|
("Username", "Nama pengguna"),
|
|
("Invalid port", "Kesalahan port"),
|
|
("Closed manually by the peer", "Ditutup secara manual oleh rekan"),
|
|
("Enable remote configuration modification", "Aktifkan modifikasi konfigurasi remotE"),
|
|
("Run without install", "Jalankan tanpa menginstal"),
|
|
("Connect via relay", "Sambungkan via relay"),
|
|
("Always connect via relay", "Selalu terhubung melalui relay"),
|
|
("whitelist_tip", "Hanya IP yang diizikan dapat mengakses"),
|
|
("Login", "Masuk"),
|
|
("Verify", "Verifikasi"),
|
|
("Remember me", "Ingatkan saya"),
|
|
("Trust this device", "Izinkan perangkat ini"),
|
|
("Verification code", "Kode verifikasi"),
|
|
("verification_tip", "Kode verifikasi sudah dikirim ke email yang terdaftar, masukkan kode verifikasi untuk melanjutkan."),
|
|
("Logout", "Keluar"),
|
|
("Tags", "Tag"),
|
|
("Search ID", "Cari ID"),
|
|
("whitelist_sep", "Dipisahkan dengan koma, titik koma, spasi, atau baris baru"),
|
|
("Add ID", "Tambah ID"),
|
|
("Add Tag", "Tambah Tag"),
|
|
("Unselect all tags", "Batalkan pilihan semua tag"),
|
|
("Network error", "Kesalahan Jaringan"),
|
|
("Username missed", "Nama pengguna tidak sesuai"),
|
|
("Password missed", "Kata sandi tidak sesuai"),
|
|
("Wrong credentials", "Nama pengguna atau kata sandi salah"),
|
|
("The verification code is incorrect or has expired", "Kode verifikasi salah atau sudah kadaluarsa"),
|
|
("Edit Tag", "Ubah Tag"),
|
|
("Forget Password", "Lupakan Kata Sandi"),
|
|
("Favorites", "Favorit"),
|
|
("Add to Favorites", "Tambah ke Favorit"),
|
|
("Remove from Favorites", "Hapus dari favorit"),
|
|
("Empty", "Kosong"),
|
|
("Invalid folder name", "Nama folder tidak valid"),
|
|
("Socks5 Proxy", "Proksi Socks5"),
|
|
("Socks5/Http(s) Proxy", "Proksi Socks5/Http(s)"),
|
|
("Discovered", "Telah ditemukan"),
|
|
("install_daemon_tip", "Untuk dapat berjalan saat sistem menyala, kamu perlu menginstal layanan sistem (system service/daemon)."),
|
|
("Remote ID", "ID Remote"),
|
|
("Paste", "Tempel"),
|
|
("Paste here?", "Tempel disini?"),
|
|
("Are you sure to close the connection?", "Apakah kamu yakin akan menutup koneksi?"),
|
|
("Download new version", "Download versi baru"),
|
|
("Touch mode", "Mode Layar Sentuh"),
|
|
("Mouse mode", "Mode Mouse"),
|
|
("One-Finger Tap", "Ketuk Satu Jari"),
|
|
("Left Mouse", "Mouse Kiri"),
|
|
("One-Long Tap", "Ketuk Tahan"),
|
|
("Two-Finger Tap", "Ketuk Dua Jari"),
|
|
("Right Mouse", "Mouse Kanan"),
|
|
("One-Finger Move", "Gerakan Satu Jari"),
|
|
("Double Tap & Move", "Ketuk Dua Kali & Pindah"),
|
|
("Mouse Drag", "Geser Mouse"),
|
|
("Three-Finger vertically", "Tiga Jari secara vertikal"),
|
|
("Mouse Wheel", "Roda mouse"),
|
|
("Two-Finger Move", "Gerakan Dua Jari"),
|
|
("Canvas Move", "Gerakan Kanvas"),
|
|
("Pinch to Zoom", "Cubit untuk Memperbesar"),
|
|
("Canvas Zoom", "Perbesar Canvas"),
|
|
("Reset canvas", "Setel Ulang Canvas"),
|
|
("No permission of file transfer", "Tidak ada izin untuk mengirim file"),
|
|
("Note", "Catatan"),
|
|
("Connection", "Koneksi"),
|
|
("Share screen", "Bagikan Layar"),
|
|
("Chat", "Obrolan"),
|
|
("Total", "Total"),
|
|
("items", "item"),
|
|
("Selected", "Dipilih"),
|
|
("Screen Capture", "Tangkapan Layar"),
|
|
("Input Control", "Kontrol input"),
|
|
("Audio Capture", "Rekam Suara"),
|
|
("Do you accept?", "Apakah kamu setuju?"),
|
|
("Open System Setting", "Buka Pengaturan Sistem"),
|
|
("How to get Android input permission?", "Bagaimana cara mendapatkan izin input dari Android?"),
|
|
("android_input_permission_tip1", "Agar perangkat jarak jauh dapat mengontrol perangkat Android melalui mouse atau sentuhan, Kamu harus memberikan izin/permission kd RustDesk untuk menggunakan layanan \"Aksesibilitas\"."),
|
|
("android_input_permission_tip2", "Silakan buka halaman pengaturan sistem berikutnya, temukan dan masuk ke [Layanan Terinstal], aktifkan layanan [Input RustDesk]."),
|
|
("android_new_connection_tip", "Permintaan akses remote telah diterima"),
|
|
("android_service_will_start_tip", "Mengaktifkan \"Tangkapan Layar\" akan memulai secara otomatis, memungkinkan perangkat lain untuk meminta koneksi ke perangkat Anda."),
|
|
("android_stop_service_tip", "Menutup layanan secara otomatis akan menutup semua koneksi yang dibuat."),
|
|
("android_version_audio_tip", "Versi Android saat ini tidak mendukung pengambilan audio, harap tingkatkan ke Android 10 atau lebih tinggi."),
|
|
("android_start_service_tip", "Tap [Mulai Layanan] atau aktifkan izin [Tangkapan Layar] untuk memulai berbagi layar."),
|
|
("android_permission_may_not_change_tip", "Izin untuk koneksi yang sudah terhubung mungkin tidak dapat diubah secara instan hingga terhubung kembali"),
|
|
("Account", "Akun"),
|
|
("Overwrite", "Ganti"),
|
|
("This file exists, skip or overwrite this file?", "File ini sudah ada, lewati atau ganti file ini?"),
|
|
("Quit", "Keluar"),
|
|
("Help", "Bantuan"),
|
|
("Failed", "Gagal"),
|
|
("Succeeded", "Berhasil"),
|
|
("Someone turns on privacy mode, exit", "Seseorang mengaktifkan mode privasi, keluar"),
|
|
("Unsupported", "Tidak didukung"),
|
|
("Peer denied", "Rekan menolak"),
|
|
("Peer exit", "Rekan keluar"),
|
|
("Failed to turn off", "Gagal mematikan"),
|
|
("Turned off", "Dimatikan"),
|
|
("Language", "Bahasa"),
|
|
("Keep RustDesk background service", "Pertahankan RustDesk berjalan pada service background"),
|
|
("Ignore Battery Optimizations", "Abaikan Pengoptimalan Baterai"),
|
|
("android_open_battery_optimizations_tip", "Jika anda ingin menonaktifkan fitur ini, buka halam pengaturan, cari dan pilih [Baterai], Uncheck [Tidak dibatasi]"),
|
|
("Start on boot", "Mulai saat dihidupkan"),
|
|
("Start the screen sharing service on boot, requires special permissions", "Mulai layanan berbagi layar saat sistem dinyalakan, memerlukan izin khusus."),
|
|
("Connection not allowed", "Koneksi tidak dizinkan"),
|
|
("Legacy mode", "Mode lawas"),
|
|
("Map mode", "Mode peta"),
|
|
("Translate mode", "Mode terjemahan"),
|
|
("Use permanent password", "Gunakan kata sandi permanaen"),
|
|
("Use both passwords", "Gunakan kedua kata sandi"),
|
|
("Set permanent password", "Setel kata sandi permanen"),
|
|
("Enable remote restart", "Aktifkan Restart Secara Remote"),
|
|
("Restart remote device", "Restart Perangkat Secara Remote"),
|
|
("Are you sure you want to restart", "Apakah Anda yakin ingin merestart"),
|
|
("Restarting remote device", "Merestart Perangkat Remote"),
|
|
("remote_restarting_tip", "Perangkat remote sedang merestart, harap tutup pesan ini dan sambungkan kembali dengan kata sandi permanen setelah beberapa saat."),
|
|
("Copied", "Disalin"),
|
|
("Exit Fullscreen", "Keluar dari Layar Penuh"),
|
|
("Fullscreen", "Layar penuh"),
|
|
("Mobile Actions", "Tindakan Seluler"),
|
|
("Select Monitor", "Pilih Monitor"),
|
|
("Control Actions", "Tindakan Kontrol"),
|
|
("Display Settings", "Pengaturan tampilan"),
|
|
("Ratio", "Rasio"),
|
|
("Image Quality", "Kualitas gambar"),
|
|
("Scroll Style", "Gaya Scroll"),
|
|
("Show Toolbar", "Tampilkan Toolbar"),
|
|
("Hide Toolbar", "Sembunyikan Toolbar"),
|
|
("Direct Connection", "Koneksi langsung"),
|
|
("Relay Connection", "Koneksi Relay"),
|
|
("Secure Connection", "Koneksi aman"),
|
|
("Insecure Connection", "Koneksi Tidak Aman"),
|
|
("Scale original", "Skala asli"),
|
|
("Scale adaptive", "Skala adaptif"),
|
|
("General", "Umum"),
|
|
("Security", "Keamanan"),
|
|
("Theme", "Tema"),
|
|
("Dark Theme", "Tema Gelap"),
|
|
("Light Theme", "Tema Terang"),
|
|
("Dark", "Gelap"),
|
|
("Light", "Terang"),
|
|
("Follow System", "Ikuti Sistem"),
|
|
("Enable hardware codec", "Aktifkan kodek perangkat keras"),
|
|
("Unlock Security Settings", "Buka Keamanan Pengaturan"),
|
|
("Enable audio", "Aktifkan Audio"),
|
|
("Unlock Network Settings", "Buka Keamanan Pengaturan Jaringan"),
|
|
("Server", "Server"),
|
|
("Direct IP Access", "Akses IP Langsung"),
|
|
("Proxy", "Proksi"),
|
|
("Apply", "Terapkan"),
|
|
("Disconnect all devices?", "Putuskan sambungan semua perangkat?"),
|
|
("Clear", "Bersihkan"),
|
|
("Audio Input Device", "Input Perangkat Audio"),
|
|
("Use IP Whitelisting", "Gunakan daftar IP yang diizinkan"),
|
|
("Network", "Jaringan"),
|
|
("Pin Toolbar", "Sematkan Toolbar"),
|
|
("Unpin Toolbar", "Batal sematkan Toolbar"),
|
|
("Recording", "Perekaman"),
|
|
("Directory", "Direktori"),
|
|
("Automatically record incoming sessions", "Otomatis merekam sesi masuk"),
|
|
("Automatically record outgoing sessions", "Rekam sesi keluar secara otomatis"),
|
|
("Change", "Ubah"),
|
|
("Start session recording", "Mulai sesi perekaman"),
|
|
("Stop session recording", "Hentikan sesi perekaman"),
|
|
("Enable recording session", "Aktifkan Sesi Perekaman"),
|
|
("Enable LAN discovery", "Aktifkan Pencarian Jaringan Lokal (LAN)"),
|
|
("Deny LAN discovery", "Tolak Pencarian Jaringan Lokal (LAN)"),
|
|
("Write a message", "Tulis pesan"),
|
|
("Prompt", "Permintaan"),
|
|
("Please wait for confirmation of UAC...", "Harap tunggu konfirmasi UAC"),
|
|
("elevated_foreground_window_tip", "Jendela yang sedang aktif di remote desktop memerlukan hak istimewa yang lebih tinggi untuk beroperasi, sehingga mouse dan keyboard tidak dapat digunakan sementara waktu. Kamu bisa meminta pengguna jarak jauh untuk meminimalkan jendela saat ini, atau klik tombol elevasi di jendela manajemen koneksi. Untuk menghindari masalah ini, disarankan untuk menginstal software di perangkat remote secara permanen."),
|
|
("Disconnected", "Terputus"),
|
|
("Other", "Lainnya"),
|
|
("Confirm before closing multiple tabs", "Konfirmasi sebelum menutup banyak tab"),
|
|
("Keyboard Settings", "Pengaturan Papan Ketik"),
|
|
("Full Access", "Akses penuh"),
|
|
("Screen Share", "Berbagi Layar"),
|
|
("ubuntu-21-04-required", "Wayland membutuhkan Ubuntu 21.04 atau versi yang lebih tinggi."),
|
|
("wayland-requires-higher-linux-version", "Wayland membutuhkan versi distro linux yang lebih tinggi. Silakan coba desktop X11 atau ubah OS Anda."),
|
|
("xdp-portal-unavailable", "Pengambilan layar Wayland gagal. XDG Desktop Portal mungkin telah crash atau tidak tersedia. Coba mulai ulang dengan `systemctl --user restart xdg-desktop-portal`."),
|
|
("JumpLink", "Tautan Cepat"),
|
|
("Please Select the screen to be shared(Operate on the peer side).", "Silakan Pilih layar yang akan dibagikan kepada rekan anda."),
|
|
("Show RustDesk", "Tampilkan RustDesk"),
|
|
("This PC", "PC ini"),
|
|
("or", "atau"),
|
|
("Elevate", "Elevasi"),
|
|
("Zoom cursor", "Perbersar Kursor"),
|
|
("Accept sessions via password", "Izinkan sesi dengan kata sandi"),
|
|
("Accept sessions via click", "Izinkan sesi dengan klik"),
|
|
("Accept sessions via both", "Izinkan sesi dengan keduanya"),
|
|
("Please wait for the remote side to accept your session request...", "Harap tunggu pihak pengguna remote untuk menerima permintaan sesi..."),
|
|
("One-time Password", "Kata sandi sementara"),
|
|
("Use one-time password", "Gunakan kata sandi sementara"),
|
|
("One-time password length", "Panjang kata sandi sementara"),
|
|
("Request access to your device", "Permintaan akses ke perangkat ini"),
|
|
("Hide connection management window", "Sembunyikan jendela pengaturan koneksi"),
|
|
("hide_cm_tip", "Izinkan untuk menyembunyikan hanya jika menerima sesi melalui kata sandi dan menggunakan kata sandi permanen"),
|
|
("wayland_experiment_tip", "Dukungan Wayland masih dalam tahap percobaan, harap gunakan X11 jika Anda memerlukan akses tanpa pengawasan"),
|
|
("Right click to select tabs", "Klik kanan untuk memilih tab"),
|
|
("Skipped", "Dilewati"),
|
|
("Add to address book", "Tambahkan ke Buku Alamat"),
|
|
("Group", "Grup"),
|
|
("Search", "Pencarian"),
|
|
("Closed manually by web console", "Ditutup secara manual dari konsol web."),
|
|
("Local keyboard type", "Tipe papan ketik"),
|
|
("Select local keyboard type", "Pilih tipe papan ketik"),
|
|
("software_render_tip", "Jika anda menggunakan kartu grafis Nvidia pada sistem linux dan jendela windows ditutup secara instan setelah terhung, silahkan ubah ke driver open-source Nouveau, dibutukan untuk merestart aplikasi"),
|
|
("Always use software rendering", "Selalu gunakan software rendering"),
|
|
("config_input", "Untuk menggunakan input keyboard remote, anda perlu memberikan izin \"Pemantauan Input\" pada RustDesk"),
|
|
("config_microphone", "Untuk berbicara secara remote, anda perlu memberikan izin \"Rekam Audio\" pada RustDesk"),
|
|
("request_elevation_tip", "Anda juga bisa meminta izin elevasi jika ada pihak pengguna remote"),
|
|
("Wait", "Tunggu"),
|
|
("Elevation Error", "Kesalahan Elevasi"),
|
|
("Ask the remote user for authentication", "Minta pihak pengguna remote untuk otentikasi"),
|
|
("Choose this if the remote account is administrator", "Pilih ini jika akun adalah \"administrator\""),
|
|
("Transmit the username and password of administrator", "Transmisikan nama pengguna dan kata sandi administrator"),
|
|
("still_click_uac_tip", "Masih memerlukan persetujuan pihak pengguna remote untuk mengklik OK pada jendela UAC RustDesk yang sedang berjalan"),
|
|
("Request Elevation", "Permintaan Elevasi"),
|
|
("wait_accept_uac_tip", "Harap tunggu pihak pengguna remote menerima jendela UAC."),
|
|
("Elevate successfully", "Elevasi berhasil"),
|
|
("uppercase", "Huruf besar"),
|
|
("lowercase", "Huruf kecil"),
|
|
("digit", "angka"),
|
|
("special character", "Karakter spesial"),
|
|
("length>=8", "panjang>=8"),
|
|
("Weak", "Lemah"),
|
|
("Medium", "Sedang"),
|
|
("Strong", "Kuat"),
|
|
("Switch Sides", "Ganti Posisi"),
|
|
("Please confirm if you want to share your desktop?", "Harap konfirmasi apakah Anda ingin berbagi layar?"),
|
|
("Display", "Tampilan"),
|
|
("Default View Style", "Gaya Tampilan Default"),
|
|
("Default Scroll Style", "Gaya Scroll Default"),
|
|
("Default Image Quality", "Kualitas Gambar Default"),
|
|
("Default Codec", "Kodek default"),
|
|
("Bitrate", "Bitrate"),
|
|
("FPS", "FPS"),
|
|
("Auto", "Otomatis"),
|
|
("Other Default Options", "Opsi Default Lainnya"),
|
|
("Voice call", "Panggilan suara"),
|
|
("Text chat", "Obrolan Teks"),
|
|
("Stop voice call", "Hentikan panggilan suara"),
|
|
("relay_hint_tip", "Tidak memungkinkan untuk terhubung secara langsung; anda bisa mencoba terhubung via relay. Selain itu, jika ingin menggunakan relay pada percobaan pertama, silahkan tambah akhiran \"/r\" pada ID atau pilih \"Selalu terhubung via relay\" di pilihan sesi terbaru."),
|
|
("Reconnect", "Sambungkan ulang"),
|
|
("Codec", "Kodek"),
|
|
("Resolution", "Resolusi"),
|
|
("No transfers in progress", "Tidak ada proses transfer data"),
|
|
("Set one-time password length", "Atur panjang kata sandi sekali pakai"),
|
|
("RDP Settings", "Pengaturan RDP"),
|
|
("Sort by", "Urutkan berdasarkan"),
|
|
("New Connection", "Koneksi baru"),
|
|
("Restore", "Mengembalikan"),
|
|
("Minimize", "Meminimalkan"),
|
|
("Maximize", "Memaksimalkan"),
|
|
("Your Device", "Perangkat anda"),
|
|
("empty_recent_tip", "Tidak ada sesi terbaru!"),
|
|
("empty_favorite_tip", "Belum ada rekan favorit?\nTemukan seseorang untuk terhubung dan tambahkan ke favorit!"),
|
|
("empty_lan_tip", "Sepertinya kami belum memiliki rekan"),
|
|
("empty_address_book_tip", "Tampaknya saat ini tidak ada rekan yang terdaftar dalam buku alamat Anda"),
|
|
("Empty Username", "Nama pengguna kosong"),
|
|
("Empty Password", "Kata sandi kosong"),
|
|
("Me", "Saya"),
|
|
("identical_file_tip", "Data ini identik dengan milik rekan"),
|
|
("show_monitors_tip", "Tampilkan monitor di toolbar"),
|
|
("View Mode", "Mode Tampilan"),
|
|
("verify_rustdesk_password_tip", "Verifikasi Kata Sandi RustDesk"),
|
|
("No need to elevate", "Tidak perlu elevasi"),
|
|
("System Sound", "Suara Sistem"),
|
|
("Default", "Default"),
|
|
("New RDP", "RDP Baru"),
|
|
("Fingerprint", "Sidik jari"),
|
|
("Copy Fingerprint", "Salin sidik jari"),
|
|
("no fingerprints", "Tidak ada sidik jari"),
|
|
("Update", "Perbarui"),
|
|
("resolution_original_tip", "Resolusi original"),
|
|
("resolution_fit_local_tip", "Sesuaikan resolusi lokal"),
|
|
("resolution_custom_tip", "Resolusi kustom"),
|
|
("Collapse toolbar", "Ciutkan bilah alat"),
|
|
("Accept and Elevate", "Terima dan Elevasi"),
|
|
("accept_and_elevate_btn_tooltip", "Terima koneksi dan elevasi izin UAC"),
|
|
("clipboard_wait_response_timeout_tip", "Batas waktu habis saat menunggu respons salinan"),
|
|
("Incoming connection", "Koneksi akan masuk"),
|
|
("Outgoing connection", "Koneksi akan keluar"),
|
|
("Exit", "Keluar"),
|
|
("Open", "Buka"),
|
|
("logout_tip", "Apakah Anda yakin ingin keluar?"),
|
|
("Service", "Service"),
|
|
("Start", "Jalankan"),
|
|
("Stop", "Hentikan"),
|
|
("exceed_max_devices", "Anda telah mencapai jumlah maksimal perangkat yang dikelola"),
|
|
("Sync with recent sessions", "Sinkronkan dengan sesi terbaru"),
|
|
("Sort tags", "Urutkan tag"),
|
|
("Open connection in new tab", "Buka koneksi di tab baru"),
|
|
("Move tab to new window", "Pindahkan tab ke jendela baru"),
|
|
("Can not be empty", "Tidak boleh kosong"),
|
|
("Already exists", "Sudah ada"),
|
|
("Change Password", "Ganti kata sandi"),
|
|
("Refresh Password", "Perbarui Kata Sandi"),
|
|
("ID", "ID"),
|
|
("Grid View", "Tampilan Kotak"),
|
|
("List View", "Tampilan Daftar"),
|
|
("Select", "Pilih"),
|
|
("Toggle Tags", "Toggle Tag"),
|
|
("pull_ab_failed_tip", "Gagal memuat ulang buku alamat"),
|
|
("push_ab_failed_tip", "Gagal menyinkronkan buku alamat ke server"),
|
|
("synced_peer_readded_tip", "Perangkat yang terdaftar dalam sesi terbaru akan di-sinkronkan kembali ke buku alamat."),
|
|
("Change Color", "Ganti warna"),
|
|
("Primary Color", "Warna utama"),
|
|
("HSV Color", "Warna HSV"),
|
|
("Installation Successful!", "Instalasi berhasil!"),
|
|
("Installation failed!", "Instalasi gagal!"),
|
|
("Reverse mouse wheel", "Balikkan arah scroll mouse"),
|
|
("{} sessions", "sesi {}"),
|
|
("scam_title", "Kemungkinan anda Sedang DITIPU!"),
|
|
("scam_text1", "Jika anda sedang berbicara di telepon dengan seseorang yang TIDAK dikenal dan mereka meminta anda untuk menggunakan RustDesk, jangan lanjutkan dan segera tutup panggilan."),
|
|
("scam_text2", "Kemungkinan besar mereka adalah komplotan penipu yang berusaha mencuri uang atau informasi pribadi anda."),
|
|
("Don't show again", "Jangan tampilkan lagi"),
|
|
("I Agree", "Saya setuju"),
|
|
("Decline", "Tolak"),
|
|
("Timeout in minutes", "Batasan Waktu dalam Menit"),
|
|
("auto_disconnect_option_tip", "Secara otomatis akan menutup sesi ketika tidak ada aktivitas"),
|
|
("Connection failed due to inactivity", "Secara otomatis akan terputus ketik tidak ada aktivitas."),
|
|
("Check for software update on startup", "Periksa pembaruan aplikasi saat sistem dinyalakan."),
|
|
("upgrade_rustdesk_server_pro_to_{}_tip", "Silahkan perbarui RustDesk Server Pro ke versi {} atau yang lebih baru!"),
|
|
("pull_group_failed_tip", "Gagal memperbarui grup"),
|
|
("Filter by intersection", "Filter berdasarkan persilangan"),
|
|
("Remove wallpaper during incoming sessions", "Hilangkan latar dinding ketika ada sesi yang masuk"),
|
|
("Test", "Tes"),
|
|
("display_is_plugged_out_msg", "Layar terputus, pindah ke layar pertama"),
|
|
("No displays", "Tidak ada tampilan"),
|
|
("Open in new window", "Buka di jendela baru"),
|
|
("Show displays as individual windows", "Tampilkan dengan jendela terpisah"),
|
|
("Use all my displays for the remote session", "Gunakan semua layar untuk sesi remote"),
|
|
("selinux_tip", "pada perangkat anda, SELinux sedang aktif, yang mana itu dapat mencegah RustDesk berfungsi dengan baik sebagai sisi yang dikontrol."),
|
|
("Change view", "Sesuaikan tampilan"),
|
|
("Big tiles", "Kotak besar"),
|
|
("Small tiles", "Kotak kecil"),
|
|
("List", "Daftar"),
|
|
("Virtual display", "Tampilan virtual"),
|
|
("Plug out all", "Lepaskan semua"),
|
|
("True color (4:4:4)", "Warna penuh (4:4:4)"),
|
|
("Enable blocking user input", "Aktifkan pemblokiran input pengguna"),
|
|
("id_input_tip", "Anda bisa memasukkan ID, IP langsung, atau domain dengan port kostum yang sudah ditentukan (<domain>:<port>).\nJika anda ingin mengakses perangkat lain yang berbeda server, tambahkan alamat server setelah penulisan ID(<id>@<server_address>?key=<key_value>), sebagai contoh,\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nJika anda ingin mengakses perangkat yang menggunakan server publik, masukkan \"<id>@public\", server public tidak memerlukan key khusus"),
|
|
("privacy_mode_impl_mag_tip", "Mode 1"),
|
|
("privacy_mode_impl_virtual_display_tip", "Mode 2"),
|
|
("Enter privacy mode", "Masuk mode privasi"),
|
|
("Exit privacy mode", "Keluar mode privasi"),
|
|
("idd_not_support_under_win10_2004_tip", "Driver grafis yang Anda gunakan tidak kompatibel dengan versi Windows Anda dan memerlukan Windows 10 versi 2004 atau yang lebih baru"),
|
|
("input_source_1_tip", "Sumber input 1"),
|
|
("input_source_2_tip", "Sumber input 2"),
|
|
("Swap control-command key", "Menukar tombol control-command"),
|
|
("swap-left-right-mouse", "Tukar fungsi tombol kiri dan kanan pada mouse"),
|
|
("2FA code", "Kode 2FA"),
|
|
("More", "Lainnya"),
|
|
("enable-2fa-title", "Aktifkan autentikasi 2FA"),
|
|
("enable-2fa-desc", "Silakan atur autentikator Anda sekarang. Anda dapat menggunakan aplikasi autentikator seperti Authy, Microsoft Authenticator, atau Google Authenticator di ponsel atau desktop Anda\n\nPindai kode QR dengan aplikasi Anda dan masukkan kode yang ditampilkan oleh aplikasi untuk mengaktifkan autentikasi 2FA."),
|
|
("wrong-2fa-code", "Tidak dapat memverifikasi kode. Pastikan bahwa kode dan pengaturan waktu lokal sudah sesuai"),
|
|
("enter-2fa-title", "Autentikasi dua faktor"),
|
|
("Email verification code must be 6 characters.", "Kode verifikasi email harus terdiri dari 6 karakter."),
|
|
("2FA code must be 6 digits.", "Kode 2FA harus terdiri dari 6 digit."),
|
|
("Multiple Windows sessions found", "Terdapat beberapa sesi Windows"),
|
|
("Please select the session you want to connect to", "Silakan pilih sesi yang ingin Anda sambungkan."),
|
|
("powered_by_me", "Didukung oleh RustDesk"),
|
|
("outgoing_only_desk_tip", "Ini adalah edisi yang sudah kustomisasi.\nAnda dapat terhubung ke perangkat lain, tetapi perangkat lain tidak dapat terhubung ke perangkat Anda."),
|
|
("preset_password_warning", "Edisi yang dikustomisasi ini dilengkapi dengan kata sandi bawaan. Siapa pun yang mengetahui kata sandi ini dapat memperoleh kontrol penuh atas perangkat Anda. Jika Anda tidak mengharapkan ini, segera hapus pemasangan aplikasi tersebut."),
|
|
("Security Alert", "Peringatan Keamanan"),
|
|
("My address book", "Daftar Kontak"),
|
|
("Personal", "Personal"),
|
|
("Owner", "Pemilik"),
|
|
("Set shared password", "Atus kata sandi kolaboratif"),
|
|
("Exist in", "Ada di"),
|
|
("Read-only", "Hanya baca"),
|
|
("Read/Write", "Baca/Tulis"),
|
|
("Full Control", "Kontrol penuh"),
|
|
("share_warning_tip", "Informasi di atas bersifat publik dan dapat dilihat oleh orang lain."),
|
|
("Everyone", "Semua orang"),
|
|
("ab_web_console_tip", "Detail Lain di Konsol Web"),
|
|
("allow-only-conn-window-open-tip", "Koneksi hanya diperbolehkan jika jendela RustDesk sedang terbuka."),
|
|
("no_need_privacy_mode_no_physical_displays_tip", "Karena tidak ada layar fisik, mode privasi tidak perlu diaktifkan."),
|
|
("Follow remote cursor", "Ikuti kursor yang terhubung"),
|
|
("Follow remote window focus", "Ikuti jendela remote yang sedang aktif"),
|
|
("default_proxy_tip", "Pengaturan standar untuk protokol dan port adalah Socks5 dan 1080."),
|
|
("no_audio_input_device_tip", "Perangkat input audio tidak terdeteksi."),
|
|
("Incoming", "Masuk"),
|
|
("Outgoing", "Keluar"),
|
|
("Clear Wayland screen selection", "Kosongkan pilihan layar Wayland"),
|
|
("clear_Wayland_screen_selection_tip", "Setelah mengosongkan pilihan layar, Kamu bisa memilih kembali layar untuk dibagi"),
|
|
("confirm_clear_Wayland_screen_selection_tip", "Kamu yakin ingin membersihkan pemilihan layar Wayland?"),
|
|
("android_new_voice_call_tip", "Kamu mendapatkan permintaan panggilan suara baru. Jika diterima, audio akan berubah menjadi komunikasi suara."),
|
|
("texture_render_tip", "Aktifkan rendering tekstur untuk membuat tampilan gambar lebih mulus. Kamu dapat menonaktifkan opsi ini jika terjadi masalah saat merender."),
|
|
("Use texture rendering", "Aktifkan rendering tekstur"),
|
|
("Floating window", "Jendela mengambang"),
|
|
("floating_window_tip", "Untuk menjaga layanan/service RustDesk agar tetap aktif"),
|
|
("Keep screen on", "Biarkan layar tetap menyala"),
|
|
("Never", "Tidak pernah"),
|
|
("During controlled", "Dalam proses pengendalian"),
|
|
("During service is on", "Saat layanan aktif"),
|
|
("Capture screen using DirectX", "Rekam layar dengan DirectX"),
|
|
("Back", "Kembali"),
|
|
("Apps", "App"),
|
|
("Volume up", "Naikkan volume"),
|
|
("Volume down", "Turunkan volume"),
|
|
("Power", "Daya"),
|
|
("Telegram bot", "Bot Telegram"),
|
|
("enable-bot-tip", "Jika fitur ini diaktifkan, Kamu dapat menerima kode 2FA dari bot, serta mendapatkan notifikasi tentang koneksi."),
|
|
("enable-bot-desc", "1. Buka chat dengan @BotFather.\n2. Kirim perintah \"/newbot\". Setelah menyelesaikan langkah ini, Kamu akan mendapatkan token\n3. Mulai percakapan dengan bot yang baru dibuat. Kirim pesan yang dimulai dengan garis miring (\"/\") seperti \"/hello\" untuk mengaktifkannya."),
|
|
("cancel-2fa-confirm-tip", "Apakah Kamu yakin ingin membatalkan 2FA?"),
|
|
("cancel-bot-confirm-tip", "Apakah Kamu yakin ingin membatalkan bot Telegram?"),
|
|
("About RustDesk", "Tentang RustDesk"),
|
|
("Send clipboard keystrokes", "Kirim keystrokes clipboard"),
|
|
("network_error_tip", "Periksa koneksi internet, lalu klik \"Coba lagi\"."),
|
|
("Unlock with PIN", "Buka menggunakan PIN"),
|
|
("Requires at least {} characters", "Memerlukan setidaknya {} karakter."),
|
|
("Wrong PIN", "PIN salah"),
|
|
("Set PIN", "Atur PIN"),
|
|
("Enable trusted devices", "Izinkan perangkat tepercaya"),
|
|
("Manage trusted devices", "Kelola perangkat tepercaya"),
|
|
("Platform", "Platform"),
|
|
("Days remaining", "Sisa hari"),
|
|
("enable-trusted-devices-tip", "Tidak memerlukan verifikasi 2FA pada perangkat tepercaya."),
|
|
("Parent directory", "Direktori utama"),
|
|
("Resume", "Lanjutkan"),
|
|
("Invalid file name", "Nama file tidak valid"),
|
|
("one-way-file-transfer-tip", "Transfer file satu arah (One-way) telah diaktifkan pada sisi yang dikendalikan."),
|
|
("Authentication Required", "Diperlukan autentikasi"),
|
|
("Authenticate", "Autentikasi"),
|
|
("web_id_input_tip", "Kamu bisa memasukkan ID pada server yang sama, akses IP langsung tidak didukung di klien web.\nJika Anda ingin mengakses perangkat di server lain, silakan tambahkan alamat server (<id>@<server_address>?key=<key_value>), contohnya:\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nUntuk mengakses perangkat di server publik, cukup masukkan \"<id>@public\", tanpa kunci/key."),
|
|
("Download", "Download"),
|
|
("Upload folder", "Upload folder"),
|
|
("Upload files", "Upload file"),
|
|
("Clipboard is synchronized", "Clipboard disinkronisasi"),
|
|
("Update client clipboard", "Perbarui papan klip klien"),
|
|
("Untagged", "Tanpa tag"),
|
|
("new-version-of-{}-tip", "Versi {} sudah tersedia."),
|
|
("Accessible devices", "Perangkat yang tersedia"),
|
|
("upgrade_remote_rustdesk_client_to_{}_tip", "Silahkan perbarui aplikasi RustDesk ke versi {} atau yang lebih baru pada komputer yang akan terhubung!"),
|
|
("d3d_render_tip", "Ketika rendering D3D diaktifkan, layar kontrol jarak jauh bisa tampak hitam di beberapa komputer"),
|
|
("Use D3D rendering", "Gunakan rendering D3D"),
|
|
("Printer", "Printer"),
|
|
("printer-os-requirement-tip", "Fungsi pencetakan keluar memerlukan Windows 10 atau yang lebih baru."),
|
|
("printer-requires-installed-{}-client-tip", "Untuk menggunakan pencetakan jarak jauh, {} perlu dipasang di perangkat ini."),
|
|
("printer-{}-not-installed-tip", "Printer {} tidak terinstal"),
|
|
("printer-{}-ready-tip", "Printer {} sudah terinstal dan siap digunakan."),
|
|
("Install {} Printer", "Pasang Printer {}"),
|
|
("Outgoing Print Jobs", "Tugas Cetak Keluar"),
|
|
("Incoming Print Jobs", "Tugas Cetak Masuk"),
|
|
("Incoming Print Job", "Tugas Cetak Masuk"),
|
|
("use-the-default-printer-tip", "Gunakan printer default"),
|
|
("use-the-selected-printer-tip", "Gunakan printer yang dipilih"),
|
|
("auto-print-tip", "Cetak otomatis menggunakan printer yang dipilih."),
|
|
("print-incoming-job-confirm-tip", "Anda menerima tugas cetak dari jarak jauh. Apakah Anda ingin menjalankannya di sisi Anda?"),
|
|
("remote-printing-disallowed-tile-tip", "Remote Printing tidak diizinkan"),
|
|
("remote-printing-disallowed-text-tip", "Komputer yang diakses tidak mengizinkan Remote Printing."),
|
|
("save-settings-tip", "Simpan pengaturan"),
|
|
("dont-show-again-tip", "Jangan tampilkan lagi"),
|
|
("Take screenshot", "Ambil tangkapan layar"),
|
|
("Taking screenshot", "Mengambil tangkapan layar"),
|
|
("screenshot-merged-screen-not-supported-tip", "Menggabungkan tangkapan layar dari beberapa tampilan saat ini tidak didukung. Silakan beralih ke satu tampilan dan coba lagi."),
|
|
("screenshot-action-tip", "Silakan pilih cara melanjutkan dengan tangkapan layar."),
|
|
("Save as", "Simpan sebagai"),
|
|
("Export", "Ekspor"),
|
|
("Export Logs", "Ekspor Log"),
|
|
("Import Folder", "Impor Folder"),
|
|
("Copy to clipboard", "Salin ke papan klip"),
|
|
("Enable remote printer", "Aktifkan printer jarak jauh"),
|
|
("Downloading {}", "Mendownload {}"),
|
|
("{} Update", "Perbarui {}"),
|
|
("{}-to-update-tip", "{} akan ditutup dan menginstal versi baru"),
|
|
("download-new-version-failed-tip", "Gagal mendownload. Kamu bisa mencoba lagi nanti atau klik tombol \"Download\" melakukan download dari halaman rilis dan meningkatkan versi secara manual."),
|
|
("Auto update", "Pembaruan otomatis"),
|
|
("update-failed-check-msi-tip", "Pemeriksaan metode pemasangan gagal. Silakan klik tombol \"Download\" untuk mengunduh dari halaman rilis dan tingkatkan secara manual."),
|
|
("websocket_tip", "Saat menggunakan WebSocket, hanya koneksi relay yang didukung."),
|
|
("Use WebSocket", "Gunakan WebSocket"),
|
|
("Trackpad speed", "Kecepatan trackpad"),
|
|
("Default trackpad speed", "Kecepatan default trackpad"),
|
|
("Numeric one-time password", "Kata sandi sekali pakai numerik"),
|
|
("Enable IPv6 P2P connection", "Aktifkan koneksi P2P IPv6"),
|
|
("Enable UDP hole punching", "Aktifkan UDP hole punching"),
|
|
("View camera", "Lihat Kamera"),
|
|
("Enable camera", "Aktifkan kamera"),
|
|
("No cameras", "Tidak ada kamera"),
|
|
("view_camera_unsupported_tip", "Perangkat yang terhubung tidak mendukung tampilan kamera."),
|
|
("Terminal", "Terminal"),
|
|
("Enable terminal", "Aktifkan terminal"),
|
|
("New tab", "Tab baru"),
|
|
("Keep terminal sessions on disconnect", "Pertahankan sesi terminal saat terputus"),
|
|
("Terminal (Run as administrator)", "Terminal (Jalankan sebagai administrator)"),
|
|
("terminal-admin-login-tip", "Silakan masukkan nama pengguna dan kata sandi administrator dari sisi yang dikendalikan."),
|
|
("Failed to get user token.", "Gagal mendapatkan token pengguna."),
|
|
("Incorrect username or password.", "Nama pengguna atau kata sandi salah."),
|
|
("The user is not an administrator.", "Pengguna bukanlah administrator."),
|
|
("Failed to check if the user is an administrator.", "Gagal memeriksa apakah pengguna adalah administrator."),
|
|
("Supported only in the installed version.", "Hanya didukung pada versi yang terinstal."),
|
|
("elevation_username_tip", "panduan_elevasi_nama_pengguna"),
|
|
("Preparing for installation ...", "Mempersiapkan instalasi ..."),
|
|
("Show my cursor", "Tampilkan kursor saya"),
|
|
("Scale custom", "Skala kustom"),
|
|
("Custom scale slider", "Penggeser skala kustom"),
|
|
("Decrease", "Kurangi"),
|
|
("Increase", "Tambah"),
|
|
("Show virtual mouse", "Tampilkan mouse virtual"),
|
|
("Virtual mouse size", "Ukuran mouse virtual"),
|
|
("Small", "Kecil"),
|
|
("Large", "Besar"),
|
|
("Show virtual joystick", "Tampilkan joystick virtual"),
|
|
("Edit note", "Edit catatan"),
|
|
("Alias", "Alias"),
|
|
("ScrollEdge", "Gulir Tepi"),
|
|
("Allow insecure TLS fallback", "Izinkan fallback TLS tidak aman"),
|
|
("allow-insecure-tls-fallback-tip", "Secara default, RustDesk memverifikasi sertifikat server untuk protokol yang menggunakan TLS.\nDengan opsi ini diaktifkan, RustDesk akan kembali melewati langkah verifikasi dan melanjutkan jika verifikasi gagal."),
|
|
("Disable UDP", "Nonaktifkan UDP"),
|
|
("disable-udp-tip", "Mengontrol apakah hanya menggunakan TCP.\nSaat opsi ini diaktifkan, RustDesk tidak akan menggunakan UDP 21116 lagi, TCP 21116 akan digunakan sebagai gantinya."),
|
|
("server-oss-not-support-tip", "CATATAN: RustDesk server OSS tidak menyertakan fitur ini."),
|
|
("input note here", "masukkan catatan di sini"),
|
|
("note-at-conn-end-tip", "Minta catatan di akhir koneksi"),
|
|
("Show terminal extra keys", "Tampilkan tombol tambahan terminal"),
|
|
("Relative mouse mode", "Mode mouse relatif"),
|
|
("rel-mouse-not-supported-peer-tip", "Mode Mouse Relatif tidak didukung oleh peer yang terhubung."),
|
|
("rel-mouse-not-ready-tip", "Mode Mouse Relatif belum siap. Silakan coba lagi."),
|
|
("rel-mouse-lock-failed-tip", "Gagal mengunci kursor. Mode Mouse Relatif telah dinonaktifkan."),
|
|
("rel-mouse-exit-{}-tip", "Tekan {} untuk keluar."),
|
|
("rel-mouse-permission-lost-tip", "Izin keyboard dicabut. Mode Mouse Relatif telah dinonaktifkan."),
|
|
("Changelog", "Catatan perubahan"),
|
|
("keep-awake-during-outgoing-sessions-label", "Jaga layar tetap menyala selama sesi keluar"),
|
|
("keep-awake-during-incoming-sessions-label", "Jaga layar tetap menyala selama sesi masuk"),
|
|
("Continue with {}", "Lanjutkan dengan {}"),
|
|
("Display Name", "Nama Tampilan"),
|
|
("password-hidden-tip", "Kata sandi permanen telah disetel (tersembunyi)."),
|
|
("preset-password-in-use-tip", "Kata sandi pra-setel sedang digunakan."),
|
|
("Enable privacy mode", "Aktifkan mode privasi"),
|
|
("allow-remote-toolbar-docking-any-edge", "Izinkan penambatan bilah alat jarak jauh ke tepi jendela mana pun"),
|
|
("API Token", "Token API"),
|
|
("Deploy", "Terapkan"),
|
|
("Custom ID (optional)", "ID Kustom (opsional)"),
|
|
("server_requires_deployment_tip", "Server memerlukan perangkat ini diterapkan secara eksplisit. Terapkan sekarang?"),
|
|
("The server does not require explicit deployment.", "Server tidak memerlukan penerapan eksplisit."),
|
|
("Unknown response.", "Respons tidak dikenal."),
|
|
("wayland-keyboard-input-disabled-tip", "Izinkan masukan keyboard?"),
|
|
("wayland-keyboard-input-consent-tip", "Apa yang Anda ketik di komputer jarak jauh ini (termasuk kata sandi) dapat dibaca oleh aplikasi lain di dalamnya."),
|
|
("wayland-keyboard-input-applies-to-tip", "Pilihan ini berlaku untuk:"),
|
|
("wayland-soft-keyboard-input-label", "Masukan keyboard lunak"),
|
|
("wayland-keyboard-input-reset-choice-tip", "Setel ulang pilihan masukan keyboard"),
|
|
("remember-wayland-keyboard-choice-tip", "Jangan tanya lagi untuk komputer jarak jauh ini"),
|
|
("Why this happens", "Mengapa ini terjadi"),
|
|
("Switch display", "Ganti tampilan"),
|
|
("Show monitor switch button on the main toolbar", "Tampilkan tombol pengalih monitor di bilah alat utama"),
|
|
("Show on the minimized toolbar", "Tampilkan di bilah alat yang diperkecil"),
|
|
("All monitors", "Semua monitor"),
|
|
("#{} monitor", "Monitor {}"),
|
|
("conn-e2ee-unavailable-tip", "Tidak dapat memverifikasi enkripsi ujung ke ujung.\nPerangkat jarak jauh mungkin masih disiapkan. Coba lagi nanti.\nJika ini terus terjadi, server mungkin tidak tepercaya.\nTetap lanjutkan?"),
|
|
("ID whitelisting", "Daftar ID yang diizinkan"),
|
|
("Use ID whitelisting", "Gunakan daftar ID yang diizinkan"),
|
|
("id_whitelist_tip", "Hanya ID yang diizinkan dapat mengakses"),
|
|
("id_whitelist_wildcard_tip", "Wildcard didukung: '*' cocok dengan berapa pun jumlah karakter, '?' dengan tepat satu karakter"),
|
|
("Invalid ID", "ID tidak valid"),
|
|
("Your ID is blocked by the peer", "ID Anda diblokir oleh perangkat remote"),
|
|
("Your ip is blocked by the peer", "IP Anda diblokir oleh perangkat remote"),
|
|
("id_whitelist_caveat_tip", "ID dilaporkan oleh klien yang terhubung. Daftar ini mengurangi paparan dan bukan pengganti kata sandi atau 2FA"),
|
|
("whitelist_cidr_tip", "Notasi CIDR didukung, misalnya 192.168.1.0/24"),
|
|
("Continue", "Lanjutkan"),
|
|
("Browser didn't open? Use the url below to sign in.", "Browser tidak terbuka? Gunakan URL di bawah ini untuk masuk."),
|
|
("Lock canvas", "Kunci kanvas"),
|
|
("Sync clipboard between sessions", "Sinkronkan papan klip antar sesi"),
|
|
("sync-clipboard-between-sessions-tip", "Teks atau gambar yang disalin di satu sesi jarak jauh juga dikirim ke papan klip sesi terhubung Anda yang lain."),
|
|
("terminal-clipboard-write-tip", ""),
|
|
("Allow terminal apps to copy to clipboard", ""),
|
|
("Enable", "Aktifkan"),
|
|
("Reuse one connection for port forwarding", "Gunakan ulang satu koneksi untuk penerusan port"),
|
|
("port-forward-mux-tip", "Menyalurkan semua koneksi dari satu penerusan port melalui satu koneksi ke perangkat lain, alih-alih menyambung dan masuk lagi untuk setiap koneksi."),
|
|
("Enable WebRTC P2P connection", "Aktifkan koneksi P2P WebRTC"),
|
|
("Enable TCP hole punching", "Aktifkan TCP hole punching"),
|
|
].iter().cloned().collect();
|
|
}
|