v2.2.5

Fixes from a week of running the fleet: two timing bugs that made a healthy device look slow or silent, a false clock alarm on sleeping laptops, and a small console convenience. Every component is 2.2.5.0; there is no schema change. This release also covers 2.2.3 and 2.2.4, which ran on the maintainer's fleet but were never tagged.

Highlights

• Tunnels no longer wait out ssh's ConnectTimeout. The OpenSSH 8.1 client that Windows 10 (and Server 2016/2019) ships sleeps through the whole ConnectTimeout before it notices the connection is up, so every tunnel from such a device took 8 seconds to come up on a 1 ms link (measured: 8.0 s with the option, immediate without). The device's reverse tunnel and the operator's local forward no longer set it; the agent's own deadlines bound a dead port.
• A device that answers fast is no longer "not answering". The server bound the requester to the command only after delivery, so an agent that answered before that bookkeeping finished had its answer overwritten: the console polled into "the device did not answer" while the tunnel was open, and the audit row said "?". The answer is now kept, and the audit names the real operator and device.
• A tunnel start is safe from the idle watchdog, which used to close a tunnel that was only just coming up (No process is associated with this object), and the agent logs where a slow start spends its time: launch, resolve, connect, authentication. The console's status line shows how long the device took to answer and how long the tunnel plus VNC took after that.
• A sleeping laptop is not a clock error. A report that a dozing laptop delivered late looked exactly like a clock that is behind, and the device stayed marked Error until it woke again. The server now reads the clock from the freshest of a device's recent reports and needs two agreeing ones before it calls a clock slow.
• Click a telemetry value to copy it. Hostname, addresses, make and model, serial number, device id: click the value, it is on the clipboard. The panel refreshes in place, and the public IP and its reverse name are separate rows.

Upgrading

1. Server: upload RemoteServer-linux-x64.tar.gz in Server settings → Server update, then Update server. No SQL.
2. Agent: roll it out. The idle-watchdog fix matters on every device; the ConnectTimeout fix on devices and operator PCs running Windows 10 or Server 2016/2019, where each tunnel used to take 8 seconds to come up.
3. Console: needed for click-to-copy and the connect timing in the status line. Updater, Lite and the Linux console carry the aligned version; the Linux console also gets the separate public IP / reverse name rows.

Artifacts

• RemoteAgent.exe, RemoteAgent.Updater.exe, RemoteClient.exe, RemoteClient.Lite.exe — Windows, self-contained, signed with the maintainer's Open Source Developer code-signing certificate and timestamped.
• RemoteServer-linux-x64.tar.gz — the server package for the console's Server update tab.
• remoteclient_2.2.5_amd64.deb — the Linux operator console.