Skip to content

OMARemote 0.9.13

Choose a tag to compare

@github-actions github-actions released this 22 Oct 09:43
· 19 commits to main since this release
Immutable release. Only release title and notes can be modified.

What's new in 0.9.13

  • SSH sessions reconnect by themselves. When a working connection drops (the computer restarts, you move from cable to wifi), the session starts ssh again in the same terminal, the screen and scrollback kept. A banner at the top says what happens ("Connection lost · trying again in 4 s", "reconnecting to pc.lan…"), with Try now (⏎) and Cancel. It tries with growing pauses for up to 10 minutes. It is a new shell: programs that ran on the server are gone unless they ran in tmux or screen. A refused sign-in, a host key that is not accepted or a refusal before signing in is never tried again. Reconnect is on by default and can be switched off per SSH connection.
  • Much less CPU with a session on screen. Since the first release, a hidden "Connecting…" animation kept running in every open session (RDP, VNC, Gliff and SSH alike), and the window redrew at the screen's refresh rate the whole time: some 40% of a CPU core on a 240 Hz monitor. It now only runs while a session is actually connecting.
  • A session that ended is shown on a card. The "Connection failed" / "Disconnected" panel sits on its own card over the session's last picture, dimmed, instead of across the remote text.
  • ssh failures in plain words. "client_loop: send disconnect: Broken pipe" now reads "The connection was lost: the computer may have restarted, or the network changed"; refused connections, unknown names, unreachable networks, refused sign-ins and host keys get a sentence too. ssh's own words stay in the log.

Security review

Reviewed everything since 0.9.12 against docs/security-review.md. The Reviewer session reviewed every change and ran the omarchy-plugin-security skill (built from the marketplace's own review comments) over the whole release until it found nothing more.

  • Marketplace finding #12422 (HANCORE-linux): a Gliff server could make a file paste write outside its folder. A new clipboard offer arriving while files were being pasted replaced the offer under the running paste: its next file came from the new list, with no folder, so it was created relative to where OMARemote was started (usually your home folder). Each paste now keeps its own copy of the offer and of its folder (as an open descriptor), creates every file and folder beneath that descriptor without following links (openat2), and a new offer ends every paste still running.
  • Found with the skill, all fixed:
    • Stopping a session could signal another program. omaremote-session stop signalled the process number in the session's record; after a crash that number can belong to another program. Every record now keeps its processes' start times, and a signal only goes to that same process (pinned with a pidfd first).
    • A server could grow the session log without limit. The log is in memory (the runtime folder) and the log view reads it whole. It is capped at 8 MiB, lines at 8 KiB, and the rest of a long line can no longer pass for a line of its own.
    • Files of the user's, read by name after a check. Hyprland config, known_hosts, ssh keys, terminal configs and OMARemote's own state files are now read through one open: only an ordinary file, never a FIFO that would hang, with a size limit.
    • Own files written through a planted link. The Kerberos cache and config are replaced atomically; the backups of hyprland.lua and ~/.ssh/config are created new, and when something else sits at a backup's name the config is left alone rather than edited without a backup.
  • Reconnecting cannot be steered into dialling forever. Each try is judged by its own output; 20 drops in a row with nothing typed in between end it, so a server that keeps saying "Broken pipe" cannot keep the client calling.
  • Tests that fail without each fix: the clipboard swap against the real clipboard code, process identity before signals, the log cap, FIFOs and links at file names, the backups, and SSH reconnect against the real omaremote-ssh with a stand-in ssh.
  • Left as they are (hardening, same-user only): the window reads its own backend's output and its own config files whole.

OMARemote is in early development: it works day to day, but expect rough edges. Please report what you run into: https://github.com/RFdeGroot/OMARemote/issues

Install on Omarchy, on Intel/AMD (x86_64) or Apple Silicon (aarch64); pacman pulls in every dependency:

curl -LO https://github.com/RFdeGroot/OMARemote/releases/download/v0.9.13/omaremote-0.9.13-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.13-1-$(uname -m).pkg.tar.zst

The package is signed with OMARemote's release key; OMARemote's Update button checks that before installing. To check it by hand, with the key from packaging/arch/omaremote-release.gpg in the repository: curl -L -o omaremote.sig https://github.com/RFdeGroot/OMARemote/releases/download/v0.9.13/omaremote-0.9.13-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.13-1-$(uname -m).pkg.tar.zst. Keep the signature under that other name: pacman checks a .sig it finds beside the package against its own keyring, which does not have OMARemote's key, and refuses the install.

Updating from an earlier release works the same way: pacman upgrades in place. Restart OMARemote afterwards.

Or build it from source with the attached PKGBUILD: makepkg -si. See the README for more.