Repository navigation
OMARemote 0.9.12
What's new in 0.9.12
- Fullscreen for RDP, for real. Resolution → Fullscreen now opens the connection in a window of its own that fills the screen, straight away. Choose Whole screen (the Omarchy bar hidden, only the remote desktop showing) or In a window (maximised, the bar stays). In Whole screen, rest the pointer on the top edge: a bar slides in with Exit fullscreen, To a tab and Disconnect, each with its key. Fullscreen opens in its own window, so a tab or a hotkey window is not offered with it; a hotkey window can still go fullscreen with
ctrl+alt+⏎while it is open. ctrl+alt+⏎in a tab works like Omarchy's SUPER+F. The manager goes fullscreen with the Omarchy bar hidden and keeps its own tabs, pinned list and status bar.- Windows come back where they belong. An own window leaving fullscreen comes back centred (Hyprland put it partly off the screen). A Hyprland window rule of your own for OMARemote's windows (
omaremote-session) is now respected: OMARemote no longer floats, sizes or centres them over it. - Gliff asks before trusting a new computer. The first connection to a computer used to fail with ssh's "Host key verification failed.", which read like a wrong key. The tab now asks "Trust pc.lan?" with its key's fingerprint; Trust lets ssh add it to
~/.ssh/known_hosts, as answering yes in a terminal does. A changed key is refused, as ssh refuses it, with a clear warning and how to clear the old key if the machine was reinstalled. A key of a new type for a known computer gets a warning in the question. - Gliff no longer connects to its own computer. Streaming a computer into itself only echoes itself. A connection that reaches this computer (by its address, its name, or its ssh host key) is greyed in the list, marked "this computer", and refuses to connect, also when it arrived through sync from another computer. A clone with the same ssh host keys can be marked It's another computer (this computer only, never synced, for that host and port).
- "All monitors" is gone. FreeRDP's multi-monitor mode measures every monitor wrongly on Hyprland and cannot connect. It comes back once it works; a connection that had it opens as before otherwise.
Security review
Reviewed everything since 0.9.11 against docs/security-review.md; the Reviewer session reviewed each change as it was made.
- Marketplace finding #12352 (HANCORE-linux): a server could make the session allocate without bound. Gliff's H.264 decoder took its size from the server's stream with no limit before decoding. Now a stream larger than the 3840×2160 the client asks for ends the session, and a picture larger than its stream is refused when FFmpeg first learns its size, before it allocates anything for it (
get_format, plus FFmpeg's own pixel limit). The same pass found the same class in RDP: FreeRDP's graphics pipeline let a server create surfaces up to 65535×65535 (17 GB each), as many as it liked, and copy any of them into a cache with no total. Surfaces are now capped at 8192 a side and 2 GiB together (RemoteFX tiles counted), the cache at 128 MiB (the RDP specification's limit is 100 MB). Every session process also has a 4 GiB memory ceiling for what a library might still allocate, and reaching it ends the session cleanly instead of crashing. - The new host-key question cannot be posed by a server. ssh hands a server's own login questions to the same helper; only a question that starts with ssh's own wording is shown as "Trust …?", so a server cannot bring up that dialog. Only "yes" after Trust is ever answered, and ssh itself still decides and writes known_hosts.
- Command lines stay anonymous. Finding "this computer" runs in-process (addresses, known_hosts with hashed entries, key fingerprints computed here); the only new command line with a host is a Gliff session's
ssh -Gjust before its ownssh, documented with it. - Found in this review: the Hyprland rule scan and the known_hosts reader opened files by path without checking they were regular files; a FIFO by such a name would hang the placement. Both read regular files only now, with a test that fails without the fix.
- Tests that fail without each fix: oversized streams and pictures against a fake Gliff server, the RDP surface and cache limits, the memory ceiling, the host-key question (a fake ssh using the real askpass path, and the real OpenSSH 10.6 checked by hand), and this computer's detection.
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.12/omaremote-0.9.12-1-$(uname -m).pkg.tar.zst
sudo pacman -U ./omaremote-0.9.12-1-$(uname -m).pkg.tar.zstThe 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.12/omaremote-0.9.12-1-$(uname -m).pkg.tar.zst.sig, then gpgv --keyring ./omaremote-release.gpg omaremote.sig omaremote-0.9.12-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.